Monitors the Auto Update Statistics setting for the database. Note that this monitor is disabled by default. Use overrides to enable it when necessary.
Knowledge Base article:
Summary
This monitor checks the Auto Update Statistics database setting. Since this monitor is part of the overall standard requirements, an alert would be generated if the setting does not meet the specified standard.
The query optimizer needs up-to-date and accurate statistics in order to generate good plans. In most cases, it’s best to let SQL Server maintain the statistics. If you turn “Auto Create Stats” and “Auto Update Stats”, then it is up to you to keep the statistics up-to-date somehow. Failure to do so will lead to poor query performance. Most applications should have these options ON.
Configuration
When the Auto Update Statistics setting is ON, the query optimizer updates statistics when they are used by a query and when they might be out-of-date. Statistics become out-of-date after insert, update, delete, or merge operations change the data distribution in the table or indexed view. The query optimizer determines when statistics might be out-of-date by counting the number of data modifications since the last statistics update and comparing the number of modifications to a threshold. The threshold is based on the number of rows in the table or indexed view. The query optimizer checks for out-of-date statistics before compiling a query and before executing a cached query plan. Before compiling a query, the query optimizer uses the columns, tables, and indexed views in the query predicate to determine which statistics might be out-of-date. Before executing a cached query plan, the Database Engine verifies that the query plan references up-to-date statistics. The AUTO_UPDATE_STATISTICS option applies to statistics created for indexes, single-columns in query predicates, and statistics that are created by using the CREATE STATISTICS statement. This option also applies to filtered statistics.
AUTO_UPDATE_STATISTICS {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 “OFF”.
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.
Expected value of database configuration setting. To view the set of applicable values please refer to "Configuration" section of the knowledge base article of this monitor.
ON
Generates Alerts
Defines whether the workflow generates an Alert.
Yes
Interval (seconds)
The recurring interval of time in seconds in which to run the workflow.
43200
Synchronization Time
The synchronization time specified by using a 24-hour format. May be omitted.
Timeout (seconds)
Specifies the time the workflow is allowed to run before being closed and marked as failed.
300
Timeout for query execution (seconds)
The workflow will fail and register an event, if the query execution takes longer than the specified period.
60
Timeout for database connection (seconds)
The workflow will fail and register an event, if it cannot access the database during the specified period.
Home
ENU