This is a standard missing index script that includes a create statement.
Run this script against any database. Create Statement column can be copied to a new window to create the missing index
-- Missing Indexes in current database by Index Advantage
SELECT user_seeks * avg_total_user_cost * ( avg_user_impact * 0.01 ) AS [index_advantage] ,
migs.last_user_seek ,
mid.[statement] AS [Database.Schema.Table] ,
mid.equality_columns ,
mid.inequality_columns ,
mid.included_columns ,
migs.unique_compiles ,
migs.user_seeks ,
migs.avg_total_user_cost ,
migs.avg_user_impact ,
N'CREATE NONCLUSTERED INDEX [IX_' + SUBSTRING(mid.statement,
CHARINDEX('.',
mid.statement,
CHARINDEX('.',
mid.statement)
+ 1) + 2,
LEN(mid.statement) - 3
- CHARINDEX('.',
mid.statement,
CHARINDEX('.',
mid.statement)
+ 1) + 1) + '_'
+ REPLACE(REPLACE(REPLACE(CASE WHEN mid.equality_columns IS NOT NULL
AND mid.inequality_columns IS NOT NULL
AND mid.included_columns IS NOT NULL
THEN mid.equality_columns + '_'
+ mid.inequality_columns
+ '_Includes'
WHEN mid.equality_columns IS NOT NULL
AND mid.inequality_columns IS NOT NULL
AND mid.included_columns IS NULL
THEN mid.equality_columns + '_'
+ mid.inequality_columns
WHEN mid.equality_columns IS NOT NULL
AND mid.inequality_columns IS NULL
AND mid.included_columns IS NOT NULL
THEN mid.equality_columns + '_Includes'
WHEN mid.equality_columns IS NOT NULL
AND mid.inequality_columns IS NULL
AND mid.included_columns IS NULL
THEN mid.equality_columns
WHEN mid.equality_columns IS NULL
AND mid.inequality_columns IS NOT NULL
AND mid.included_columns IS NOT NULL
THEN mid.inequality_columns
+ '_Includes'
WHEN mid.equality_columns IS NULL
AND mid.inequality_columns IS NOT NULL
AND mid.included_columns IS NULL
THEN mid.inequality_columns
END, ', ', '_'), ']', ''), '[', '') + '] '
+ N'ON ' + mid.[statement] + N' (' + ISNULL(mid.equality_columns, N'')
+ CASE WHEN mid.equality_columns IS NULL
THEN ISNULL(mid.inequality_columns, N'')
ELSE ISNULL(', ' + mid.inequality_columns, N'')
END + N') ' + ISNULL(N'INCLUDE (' + mid.included_columns + N');',
';') AS CreateStatement
FROM sys.dm_db_missing_index_group_stats AS migs WITH ( NOLOCK )
INNER JOIN sys.dm_db_missing_index_groups AS mig WITH ( NOLOCK ) ON migs.group_handle = mig.index_group_handle
INNER JOIN sys.dm_db_missing_index_details AS mid WITH ( NOLOCK ) ON mig.index_handle = mid.index_handle
WHERE mid.database_id = DB_ID()
ORDER BY index_advantage DESC; 
Are you rebuilding statistics twice on your tables? Longtime expert, Andy Warren, shows why you might be asking more work of your SQL Server than is required.
2008-07-29
9,132 reads
Optimize SQL Server non-clustered indexes and queries by considering index fields, compound indexes and SQL Server statistics' impact on non-clustered indexes.
2008-03-05
3,828 reads
Indexes directly affect the performance of database applications. This article uses analogies to describe how indexes work. The estimated execution plan feature of the Query Window is utilized to compare the performance of two queries in a batch.
2007-12-04
5,686 reads
SQL Server 2000 has indexed views, which can greatly improve database performance. However there are a number of restrictions on building the view, including the restriction against outer joins. So how can this work? New author Jean Charles Bulinckx brings us a technique that can help you get around this restriction.
2005-05-19
23,789 reads
There is nothing spectacular about using indexes per say. However, on many occasions I have come across a variety of SQL coders that never consider validating that the index they think they are using is efficient or even being used at all. We can all put indexes on the columns that we think will be required to satisfy individual queries, but how do we know if they will ever be used. You see, if the underlying table data is constructed, contains, or is ordered in a particular way, our indexes may never be used. One of the factors around the use of an index is its clustering factor and this is what this article is about.
2004-12-23
3,412 reads