- but it could be better not to create the index, because it doesn't
help (quey engine is not taking the index)
- but it could be better not to create the index, because it takes
more ressources than it helps
- but it could be better not to create the index, because the table is
written very often and ued very seldom in this way
- but it could be better not to create the index, because having too
many indexes for one table could bring down performance
- but why should the query engine write down this advices, if nobody
is interested in?
- but why is there no easy way to stop it from writing down the advices?


Lots of good points. Hopefully someone supporting "Index Advisor" in
this thread can answer them.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].