D
Dmitri Levin
Guest
I would limit the search for *unused* indexes to only very active tables, i.e. tables with high _TableStat-update Sort all tables by _TableStat-update and pick the top 20 to consider their indexes only. The rest do not matter. I would not go with xref, though that is a way to go, because most applications have code that was never used or is never used any more. Also if application is provided to you by Application partner, consult with them. Index may be not used because you are not using the module. And after you remove the index, it may be re-created back by a software upgrade. _indexstat is a good place to look. I deleted some 10 big indexes that were never used 5 years ago. But to second what Tom wrote above, I had to re-create one of those 10 indexes at the year end. Because it is used in AR program that runs once a year 
And finally, the is a similar problem to "unused" indexes -- indexes that are defined as unique that do not have to be defined as unique because other index already enforces uniqueness. That is a different story though.
Continue reading...
And finally, the is a similar problem to "unused" indexes -- indexes that are defined as unique that do not have to be defined as unique because other index already enforces uniqueness. That is a different story though.Continue reading...