Allow configuration of Fragmentation Alerts down to Table for EXCLUSIONS
The Fragmentation Alert for a database only permits on/off and low/medium/high with page count configurations.
This is far, far too high a level to be useful.
The Alert needs, at the very least, INCLUSION and EXCLUSION capabilities by table within database. An overall fragmentation low/medium/high and pages would be OK to START WITH, but It would be great to be able to go to each index and state the fragmentation limits and even whether to monitor it.
In my case, I use Idera's excellent Defrag Manager, so when I see this alert, I check that Defrag Manager is doing its job, then suppress the Alert for the DB. I would prefer to keep the alert alive, but exclude the huge table I know is being managed elsewhere. This would also enable me keep an eye on the tables under the Defrag Manager threshold (10 pages unless overridden).
Thanks.
Stephen
shared this idea
-
SAinCA_Mi9
commented
Use the same kind of regular-expression exclusion capabilities as Long Running Query, or Blocked Process. Can't be hard to port that...
I need to exclude Import and Export tables - they're very transient in content, and mean nothing in terms of harmful fragmentation.
-
Simon
commented
Within this, an exclusion of UID-keyed indices (which are usually permanently fragmented) would be very useful.