When troubleshooting performance issues on tables with a high number of indexes, the db2advis tool kind of falls flat. What we have done to get around this is to restore a backup of the database in question, drop all indexes, and then run the db2advis tool to get the best possible index for the query or queries in question. It would be really nice if the db2advis tool could have a flag which basically ignores any existing indexes to get the best possible index for the workload in question.
Why is it useful?
|Who would benefit from this IDEA?|
How should it work?
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions