Find Missing Indexes
From SQLServerPedia
|
See Also: Main_Page - Transact SQL Code Library - Index Performance Tuning
Missing IndexesThis query returns indexes that SQL Server 2005 (and higher) thinks are missing since the last restart. The "Impact" column is relative to the time of last restart and how bad SQL Server needs the index. 10 million+ is high. Use this only as a guide - remember that SQL Server isn't considering the impact of too many indexes on a high-write table. If a table has too many indexes, then insert/update/delete activity will slow down. Column order for key columns may be off. Generally, the most selective columns come first. The Included column order does not matter. Tutorial VideoIn this short tutorial video, Brent Ozar explains how to use the code to tune your environment. http://tutorials.sqlserverpedia.com/SQLServerPedia-20090330-IndexTuning3.flv T-SQL Code
SELECT sys.objects.name
, (avg_total_user_cost * avg_user_impact) * (user_seeks + user_scans) AS Impact
, 'CREATE NONCLUSTERED INDEX ix_IndexName ON ' + sys.objects.name COLLATE DATABASE_DEFAULT + ' ( ' + IsNull(mid.equality_columns, '') + CASE WHEN mid.inequality_columns IS NULL
THEN ''
ELSE CASE WHEN mid.equality_columns IS NULL
THEN ''
ELSE ',' END + mid.inequality_columns END + ' ) ' + CASE WHEN mid.included_columns IS NULL
THEN ''
ELSE 'INCLUDE (' + mid.included_columns + ')' END + ';' AS CreateIndexStatement
, mid.equality_columns
, mid.inequality_columns
, mid.included_columns
FROM sys.dm_db_missing_index_group_stats AS migs
INNER JOIN sys.dm_db_missing_index_groups AS mig ON migs.group_handle = mig.index_group_handle
INNER JOIN sys.dm_db_missing_index_details AS mid ON mig.index_handle = mid.index_handle AND mid.database_id = DB_ID()
INNER JOIN sys.objects WITH (nolock) ON mid.OBJECT_ID = sys.objects.OBJECT_ID
WHERE (migs.group_handle IN
(
SELECT TOP (500) group_handle
FROM sys.dm_db_missing_index_group_stats WITH (nolock)
ORDER BY (avg_total_user_cost * avg_user_impact) * (user_seeks + user_scans) DESC))
AND OBJECTPROPERTY(sys.objects.OBJECT_ID, 'isusertable')=1
ORDER BY 2 DESC , 3 DESC
Query Test Checklist
Tests Updated by Brent Ozar, 2009-04-01
SQLServerPedia Fan ContributionI really found Brent's tutorial helpful in tuning my SQL Server indexes. SQL 2005/2008 DMVs are an awesome tool for the SQL DBA. Below is my modified version of Brent's original query. It exposes the full table path so it's easier to identify which database the index recommendation is for. As Brent stated above, consider the impact of the additional indexes before applying. I've found it best to allow about 30 - 60 minutes before adding or removing indexes based on DMV recommendations. -- Clayton Kramer, 2009-04-09 Modified T-SQL Code/* ------------------------------------------------------------------ -- Title: FindMissingIndexes -- Author: Brent Ozar -- Date: 2009-04-01 -- Modified By: Clayton Kramer |