Identifies indexes that have the most range and table scans and singleton lookups.
Warning: This uses sys.dm_db_index_operational_stats, which gets its data from the cached metadata for each object. This is lost when the service restarts, and also at other times - for example if there is memory pressure or an index is rebuilt. Heavily used indexes are likely to remain cached, and so the information in this report should be accurate for the recent past for these indexes.
|What It Shows||Comments|
|Range scans||The cumulative number of range and table scans. This may be unavoidable, for certain types of reports, but it is worth investigating to see if adding an index makes a difference|
|Singleton lookups||The cumulative number of singleton lookups. This may be through use of a well targeted index, or it could be key lookups in an execution plan - in which case a covering index may help performance|