If the sql script Gor used was one I provided back in 2.99 days, I think the excessive number of indices can be traced to Access 2000.
A2K (mine, anyway) seems to create indices in tables for any column name with 'ID', 'CODE', and probably other strings. I end up with numerous indices in a new A2K table which I didn't explicitly set up.
The upsizing wizard dutifully created all the same indices in the sql script. I don't think all the indices in Snitz were planned.
I guessed it was a script generated after upsizing, and also guessed it might not be the most efficient. Grazman is/was just helping to make it that.
I'll remove the indexes <img src=icon_smile.gif border=0 align=middle> All other tips are welcome. Grazman used one topic per tip, that makes it easier to discuss them one by one.
<b>Pierre Gorissen </b><img src="http://www.homepages.hetnet.nl/~pgoris01/burnout.gif" border=0> <font color=purple><font size=1>A fool learns from experience... a wise man learns from others...</font id=size1></font id=purple>
Topic Locked
Posted - 09 September 2000 : 11:32:22
