After a warning about the potential performance impact of checking fragmentation on a large database, this report lists the indexes, along with their fragmentation and number of pages.
The number of pages is important, as is the manner in which the table is queried. If an index is small, or all retrievals are via lookups, fragmentation is irrelevant and will have no performance impact. If an index is large (a few thousand pages) and is scanned, fragmentation is likely to limit the throughput, so reorganising or rebuilding the indexes would be sensible.
|What It Shows||Comments|
|Type||Whether the object is a table or a view|
|Index Id||0 = A Heap|
1 = A clustered index
>1 = A non-clustered index
|Pages||The number of pages in the index|