Database | Indexes | Fragmentation

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 ShowsComments
Object Name
TypeWhether the object is a table or a view
Index Id0 = A Heap
1 = A clustered index
>1 = A non-clustered index
Index Name
% Fragmented
# Fragments
PagesThe number of pages in the index
< Database | Indexes | Statistics Database | Indexes | Lock Stats >