EX0013 : Identify fragmented indexes that need rebuilding or re-indexing | ![]() |
The topic describes the EX0013 analysis rule.
Identify fragmented indexes that need rebuilding or re-indexing
The rule checks for fragmented indexes that need rebuilding or re-indexing.
Fragmentation exists when indexes have pages in which the logical ordering, based on the key value, does not match the physical ordering inside the data file. Heavily fragmented indexes can degrade query performance and cause your application to respond slowly.
You can remedy index fragmentation by either reorganizing an index or by rebuilding an index. For partitioned indexes built on a partition scheme, you can use either of these methods on a complete index or on a single partition of an index.
The rule has a ContextOnly scope and is applied only on current server and database schema.
Name | Description | Default Value |
---|---|---|
MaximumAllowedFragmentation | Maximum allowed fragmentation for an index that to be ignored by the rule. | 5 |
MinimumPagesCount | Minimum number of pages an index must have in order to be considered by the rule. | 1000 |
MaximumFragmentationForReorgainizeIndex | Maximum fragmentation percent below which index reorganization will be suggested by the rule. Above this specified percent, rebuilding of the index will be suggested. | 30 |
The rule requires SQL Connection. If there is no connection provided, the rule will be skipped during analysis.
Explicit Rules, Performance Rules, Maintenance Rules
There is no additional info for this rule.
© Ubitsoft Ltd. All Rights Reserved.