Troy: >Have you reloaded your database reciently? There are some system tables that >keep track of what it thinks are good and bad indexes and then the query >optomizer uses that infor to decide what indexes to use. This info only gets >updated when you do a pack or reload.
Good point, but no. This is a VERY LARGE client database that I have never reloaded on my computer (I would just copy it back in from the original CD if I ever needed a smaller or fixed copy, but I've never done that yet either.) >The index on trantype is probably not a very good index to begin with because >I bet that field only has a few values in it which will create a lot of >entries on the multiple occurance entries for the index, thus makeing it a bad >index to start with. Probably true. There's about 200,000 rows in the table and only about 40 unique TranTypes. I'll bet that that's the reason why this index is slower! It's not a good candidate for an index in the first place, is it? I didn't create this database, just living with it. Maybe I'll play around with the MANOPT setting too. Karen ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
