Regards,
Dan B

Can you please explain what are the following column names suggests:

dm_ius.user_seeks AS UserSeek
dm_ius.user_scans AS UserScans
dm_ius.user_lookups AS UserLookups
dm_ius.user_updates AS UserUpdates

e.i. how does these values changes, what factors changes all above values ?

Thanks in advance.

That’s a great script (as yours always are), however I think you are missing another class of “missing indexes”, and that is indexes that don’t have stats at all. Rows are only written to dm_db_index_usage_stats when an index is used. If that index is totally un-used (even for writing to), it won’t appear in dm_db_index_usage_stats and therefore won’t be included in your script.

Try this on a production system, you might be surprised by how many rows it returns:

SELECT object_name(i.object_id) as tableName, i.name as indexName
FROM sys.indexes i
LEFT JOIN sys.dm_db_index_usage_stats s ON i.object_id = s.object_id AND i.index_id = s.index_id AND s.database_id = db_id()
WHERE objectproperty(i.object_id,’IsUserTable’) = 1 and i.index_id> 0
AND s.object_id IS NULL
AND i.is_Primary_Key = 0
AND i.is_unique_constraint = 0
AND i.is_unique = 0

–Dave (Another CFer)

Is that anyway can you provide the script to look at user tables and find out which many userseeks, userscan, userlook on Each Individual Index rather than UNUsedIndex script?

Thanks.

Leo

“You should pay attention to User Scan, User Lookup and User Update when you are going to drop index”

I would appreciate a separate article addressing these items.

Thanks,
Gary

ETL Developer

mjfii