Anyone have any thoughts about the best way to deal with Index
Advisor? Our advisor lists hundreds of indices that it thinks would
be nice to have.
What's the best way to spot the urgently needed ones? Number of
Times Requested is one I have been using. I recently noticed the
Number of Times Rebuilt column. Maybe a combination of the two would
be best.
And what's the best way to attack the list? When the programmers
report an application is slowing down, we look for recommendations
for the files in use. Other than that, my thought is to periodically
sort the list (using the 'best' sequence) and create indices for the
top 10 or 20. There are too many (and some are only used once or
twice) to create them all!
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.