OnLine choosing wrong index
Posted in 1996
A client of mine is finding that OnLine's optimiser is being dumb in its choice of index - no matter what the query, it always chooses the first index for the table that it comes to in sysindexes. Their application has the peculiarity that all indexes begin with the same key column. When we looked in sysindexes, we noticed that nearly every index had a value for nunique of 0 or 1 (UPDATE STATISTICS has definitely been run since the indexes were created and the tables populated.) Has anyone seen this behaviour and what suggestions can you offer? Version is 5.04.UC2 (going to 7.1x isn't an option for them in the short term). Thanks, akent@cix.compulink.co.uk (Andy Kent) ------------------------------------------------ Redland, Bristol, England