This monitor checks the Auto Shrink setting for this database. Since this monitor is a part of an overall standards requirement, an alert would be generated if the setting does not meet the specified standard.
Configuration
When the Auto Shrink statistics setting is ON, the database files are candidates for periodic shrinking. Both data file and log files can be automatically shrunk. Auto Shrink reduces the size of the transaction log only if the database is set to SIMPLE recovery model or if the log is backed up. When set to OFF, the database files are not automatically shrunk during periodic checks for unused space. The AUTO_SHRINK option causes files to be shrunk when more than 25 percent of the file contains unused space. The file is shrunk to a size where 25 percent of the file is unused space or to the size of the file when it was created, whichever is larger. You cannot shrink a read-only database.
Auto shrink can lead to excessive index fragmentation, transaction log size, and I/O. Use auto shrink only if the database is unlikely to grow again and you can do an ALTER INDEX … REORGANIZE after the shrink operation.
AUTO_SHRINK {ON | OFF}
Causes
A warning alert will be raised if the option does not match the required setting. Out of the box, the monitor is configured to alert when this setting is set to “ON”.
Resolutions
This issue may be resolved by:
Changing the configuration setting for this database to match the expected value.
Overriding the expected value for this unit monitor for this specific database or all databases.
Alternatively, if this monitor is not of concern for this database:
Disabling the monitor using overrides for this specific database or all databases.
Disabling the top-level aggregate configuration monitor using overrides for this specific database or all databases.
Home
ENU