Finding and Eliminating Duplicate or Overlapping Indexes
'Effective indexing is the key to keeping your queries running quickly while consuming as few resources as possible in the process. Each index that is added to a table will increase the speed of reads that are now able to utilize that index, but at the cost of speed whenever that index needs to be updated. In addition, your index maintenance processes (rebuilding/reorganizing) will now have an additional index to operate on.
SQL Server has no safeguards against indexes that duplicate behavior, and therefore a table could conceivably have any number of duplicate or overlapping indexes on it without your ever knowing they were there! This would constitute an unnecessary drain on resources that could easily be avoided. How do we easily view our current indexes and determine if duplicates exist? What about indexes that contain overlapping column lists that could be combined?'...
Trackbacks
Keine Trackbacks
Die Kommentarfunktion wurde vom Besitzer dieses Blogs in diesem Eintrag deaktiviert.
Kommentare
Ansicht der Kommentare: Linear | Verschachtelt