Any of the following conditions apply, for longer than the time you specify:

• The replica database is not synchronizing
• The replica database is not joined to the availability group, but the replica itself is joined
• The replica database is not connected to the availability group, but the replica itself is connected

Raised as High when a monitored availability group database is not healthy for longer than 30 seconds

Continuous

Automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies – in this case, when the database is healthy again.

• Suspended data movement
• Database inaccessible
• Delay caused by latency on the network
• Delay caused by load on the primary or secondary replica

Event

Event alerts are raised for incidents that occur at a specific point in time; they do not change level, or update their status to Ended.

Automatic failover occurs when the primary replica fails or goes offline for some reason. Planned manual failover and forced failover require initiation by a database administrator.

Continuous

Automatically updated from  Active  to  Ended  when the condition that caused the alert to be raised no longer applies – in this case, when the listener is online again.

• The IP address of the listener is offline
• There's a networking or cluster problem
• The listener's port is no longer available

Raised as Medium when a monitored availability group is not healthy for longer than 30 seconds

Continuous

Automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies – in this case, when the availability group replica is ready for automatic failover again.

Raised as Medium when the transaction delay is more than 10000 ms for longer than 120 seconds

Continuous

Automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies – in this case, when the transaction delay falls below the given threshold.

In synchronous-commit mode, the primary replica doesn’t commit any transactions until it receives acknowledgement that all synchronous secondary replicas have finished hardening the commit in their log, resulting in transaction delay.

Several factors can affect transaction delay:

• Flow control time
• Log bytes received/sec
• Log bytes flushed/sec (on the secondary replica)

Any of the following conditions apply, for longer than the time you specify:

• The replica is not connected
• The replica is not joined
• The replica is not operational as a primary or secondary replica

Raised as High when a monitored availability replica is not healthy for longer than 30 seconds

Continuous

Automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies – in this case, when the availability group replica is healthy again.

• Mismatched encryption type or algorithm
• Disconnected transport
• Another application is using the connection port
• The connection endpoint was deleted, or wasn't started

Raised as Medium when the sum of the log send queue and the redo queue is more than 100 MB for longer than 120 seconds

Continuous

Automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies – in this case, when the sum of the log send queue and the redo queue falls below the given threshold.

• Slow network connection
• The primary or secondary replica is overloaded, meaning transaction log records can't be sent
• The secondary replica is experiencing resource problems, which increases the time it takes to redo the log entries received from the primary replica

Raised when:

Either of the following conditions apply:

• No entry for a full database backup of this database in the [msdb].[dbo].[backupset] system table.
• The most recent entry for a full database backup of this database in the [msdb].[dbo].[backupset] system table is older than a specified time.

If a database belongs to an availability group, the alert is only raised on the copy of the database on the primary replica.   The alert is raised when all   entries for a full database backup for all copies of a particular database are older than the time threshold specified for the copy of the database that is on the primary replica.

Configurable thresholds:

Most recent backup is older than x seconds/minutes/hours/days

Default settings:

Raised as Medium when the last full backup is older than 7 days

Type:

Continuous

Continuous alerts can have multiple thresholds and are automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies - in this case, when a full backup is detected.

Possible causes:

• No backup job scheduled.
• Backup jobs not running or not completing. Check Job failing alerts on this SQL Server instance.
• SQL Server Agent Service is not started - check for any SQL Server Agent Service status alerts.

Raised when:

A SQL process has been blocking one or more other processes for longer than a specified duration.

Configurable thresholds:

SQL process has been blocking one or more other processes for longer than x seconds/minutes/hours/days

Default settings:

Raised as Low when a SQL process has been blocking one or more other processes for longer than a total of 60 seconds

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies - in this case, when the block ends.

Possible causes:

• Long-running queries.
• Using Insert, Update or Delete on large numbers of records in a single transaction.
• Canceling queries, but not rolling them back.

Raised when:

The active node of a cluster changes to a different node.

Configurable thresholds:

None

Default settings:

Raised as Medium

Type:

Event

Event alerts are raised for incidents that occur at a specific point in time; they do not change level, or update their status to Ended.

Possible causes:

The previously active node has failed or been manually switched to a different node.

Raised when:

The database state is something other than Online, for longer than the time you specify

Configurable thresholds:

Database unavailable for longer than x seconds/minutes/hours/days

Default settings:

Type:

Continuous

Automatically updated from Active to Ended when the database state changes back to Online.

Possible causes:

Database has been manually removed, or has encountered a problem causing its state to change to Suspect, Emergency, Recovering or Restoring.

Raised when:

SQL deadlock is detected.

Configurable thresholds:

None

Default settings:

Raised as Medium

Type:

Event

Event alerts are raised for incidents that occur at a specific point in time; they do not change level, or update their status to Ended.

Possible causes:

• Inefficient application code.
• Application accesses objects in a different order each time.
• User input during transactions.
• Lengthy transactions.
• Locks not being released as early as possible.

Raised when:

SQL Monitor is unable to turn on the deadlock trace flag on a SQL Server instance (1204 for SQL Server 2000, 1222 for SQL Server 2005 and later). This means deadlock alerts can't be raised.

Configurable thresholds:

None

Default settings:

Raised as High

Type:

Continuous

Automatically updated from Active to Ended when SQL Monitor can enable the trace flag.

Possible causes:

Insufficient privileges for the account used to connect to the SQL Server instance.

SQL Monitor requires sysadmin permissions on this account to turn on the deadlock trace flag.

Raised when:

Both of the following conditions apply:

• Fragmentation of one or more indexes in a database exceeds a percentage threshold.
• The fragmented indexes contain more than a specified number of pages.

Configurable thresholds:

Percentage fragmentation level

Indexes contain more than x pages

Default settings:

Raised as Medium when index fragmentation is above 60% for indexes with more than 1000 pages

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies - in this case, when there are no fragmented indexes (based on the thresholds defined) for the database.

Possible causes:

Regular deleting or updating existing rows or values in a table.

Notes:

Checking for index fragmentation is a very resource-intensive activity.

For this reason, SQL Monitor only checks for fragmented indexes once a week: on Sunday 02:00.

This means that the alert may remain Active for some time after you fix the issue, and will only be updated after the next scheduled weekly check.

Raised when:

Either of the following conditions apply:

• No entry for an integrity check found following DBCC DBINFO WITH TABLERESULTS.
• The most recent entry for an integrity check is older than a specified time.

Configurable thresholds:

Most recent integrity check is older than x seconds/minutes/hours/days

Default settings:

Alert is disabled by default

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies - in this case, when an integrity check of the database (DBCC CHECKDB) is detected.

Possible causes:

No integrity check has been carried out on a database, or the most recent integrity check was too long ago.

Raised when:

The job execution time is different from the baseline duration (the median of the last ten runs) by a specified percentage.

Configurable thresholds:

Percentage difference from baseline duration (either slower or quicker).

Ignore jobs with run times less than x seconds.

Default settings:

These defaults assume that once the baseline for a job is established, that job should not start running significantly more slowly or more quickly.

• Raised as Low when duration is 50% different to baseline
• Escalated to Medium when duration is 60% different to baseline
• Escalated to High when duration is 70% different to baseline
• Ignore jobs that run for less than 2 seconds.

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the job next completes with a duration that is within the allowed percentage of the baseline duration.

Possible causes:

• High system load
• Sub-optimal SQL execution plan
• Job is waiting on an event or blocked

Notes:

SQL Monitor calculates the baseline duration by using the job history to find the last ten run times.

SQL Monitor will not raise the Job duration unusual alert until the job history contains at least ten runs.

Raised when:

Job does not complete successfully, and returns error code.

Configurable thresholds:

None

Default settings:

Raised as Medium

Type:

Continuous

Automatically updated from Active to Ended when the job runs successfully again, or when the job runs again and fails (in which case the original alert will be marked as Ended and a new alert will be raised).

Possible causes:

Check the Job outcome message for a raised alert to help determine the problem.

Raised when:

Either of the following conditions apply:

• No entry for a transaction log backup of this database in the [msdb].[dbo].[backupset] system table.
• The most recent entry for a transaction log backup of this database in the [msdb].[dbo].[backupset] system table is older than a specified time.

If a database belongs to an availability group, the alert is only raised on the copy of the database on the primary replica. The alert is raised when all   entries for a transaction log backup for all copies of a particular database are older than the time threshold specified for the copy of the database that is on the primary replica.

Configurable thresholds:

Most recent backup is older than x seconds/minutes/hours/days

Default settings:

Raised as Medium when the last log backup is older than 7 days

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the condition that caused the alert to be raised no longer applies - in this case, when a transaction log backup is detected.

Possible causes:

• No log backup job scheduled.
• Log backup jobs not running or not completing. Check Job failing alerts on this SQL Server instance.
• SQL Server Agent Service is not started - check for any SQL Server Agent Service status alerts.

Raised when:

Query has been running for longer than a specified duration.

Configurable thresholds:

Query duration is longer than x seconds/minutes/hours/days

Do not raise alerts for queries that contain certain strings (matching specified regular expressions).

Default settings:

Raised as Low when a query runs longer than 10 minutes

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when the query completes.

Possible causes:

• Complex query
• Insufficient physical memory
• CPU over-utilized

Raised when:

One of the following conditions applies continuously for longer than a specified duration:

• Problems with WMI
• File sharing issues
• SQL connectivity issues

Configurable thresholds:

SQL Monitor cannot collect SQL Server data for longer than x seconds/minutes/hours/days

Default settings:

Raised as Medium

Type:

Continuous

Automatically updated from Active to Ended when data can be collected from the instance again.

Possible causes:

• One of the required services (WMI or RPC) has been stopped.
• Remote file access permissions have changed or hidden administrative shares have been disabled.
• SQL Server Service has been stopped.

Raised when:

SQL Monitor is unable to collect monitoring data from the SQL Server because the credentials supplied to connect to the instance are invalid or lack permissions.

Configurable thresholds:

SQL Server instance cannot be contacted for longer than x seconds/minutes/hours/days

Default settings:

Raised as High

Type:

Continuous

Automatically updated from Active to Ended once the correct credentials are entered and authentication is confirmed.

Possible causes:

• Your user name or password has been changed.
• Your permissions have changed and are no longer sufficient.

Raised when:

PAGE_VERIFY is set to NONE (SQL Server 2005 or SQL Server 2008) or TORN_PAGE_DETECTION is set to FALSE (SQL Server 2000) for a database.

Configurable thresholds:

None

Default settings:

Alert is disabled by default

Type:

Continuous

Automatically updated from Active to Ended when SQL Monitor detects that Page verification has been turned on.

Possible causes:

New databases inherit this setting from the Model database. Check that Page Verify is turned on for the Model databases, if required.

Raised when:

SQL Server Agent Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

Raised when:

SQL Server Analysis Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

Raised when:

An error message has been written to the SQL Server error log with a severity level above a specified value.

Configurable thresholds:

Error severity equal to or higher than x

Default settings:

Raised as Medium for errors with severity level equal to or greater than 20

Type:

Event

Event alerts are raised for incidents that occur at a specific point in time; they do not change level, or update their status to Ended.

Possible causes:

Various

Check the SQL Server error log entry area of the alert to see the error message text.

Raised when:

SQL Server Full Text Search Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

Raised when:

The SQL Server instance cannot be reached by SQL Monitor because it is not running, or because of some other error (other than permissions), for longer than the time you specify.

Configurable thresholds:

SQL Server instance unreachable for longer than x  seconds/minutes/hours/days

Default settings:

Raised as High when the SQL Server instance is unavailable for longer than 30 seconds

Type:

Continuous

Automatically updated from Active to Ended when SQL Monitor can contact the SQL Server instance.

Possible causes:

• Host machine unreachable
• SQL Server service failed
• SQL Server service manually stopped

  Check the list of component services on the relevant Windows machine. Check for Machine unreachable alerts.

Raised when:

SQL Server Reporting Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

Raised when:

The difference between the Base Monitor clock time and the monitored server clock time is greater than 15 seconds.

(The Base Monitor is the server which is running the monitoring service)

Configurable thresholds:

None

Note: This alert is always raised as Medium.

Default settings:

Time difference greater than 15 seconds. 

Type:

Continuous

Automatically updated from Active to Ended when the times are synchronized (within 15 seconds of each other).

Possible causes:

Server times across your network have not been fully synchronized.

Raised when:

SQL Monitor has problems collecting custom metric data.

Configurable thresholds:

None

Default settings:

Raised as Medium

Type:

Continuous

Automatically updated from Active to Ended when data can be collected from the database again.

Possible causes:

The most likely cause is a problem with the custom metric's T-SQL query.

Raised when:

One of the following conditions apply, depending on how you configure the alert:

• logical disk space used is above a percentage threshold, OR
• logical disk space available is less than a fixed value.

Configurable thresholds:

You can configure this alert in two ways:

• Used disk space percentage, or
• Disk space available (in MB or GB).

  Low disk space has lasted longer than x seconds.

Default settings:

Disk space available:

• Raised as Medium when less than 1GB available for longer than 60 seconds

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when disk space is above the lowest defined threshold for at least the specified duration.

Possible causes:

• Database and log files may be growing too large without frequent backups.
• Other applications may be using the disk drive for file storage.

Note:

SQL Monitor only collects disk space data at 15-second intervals:

• the minimum value for the duration is 15 seconds.
• when you configure the alert, change the duration value by 15 second increments.

Raised when:

The Windows server (host machine) does not respond to a WMI request from SQL Monitor for longer than the time you specify.

Configurable thresholds:

Machine is unreachable for longer than x  seconds/minutes/hours/days

Default settings:

Raised as High  when the host Windows machine is unavailable for longer than 30 seconds

Type:

Continuous

Automatically updated from Active to Ended when SQL Monitor can contact the host machine.

Possible causes:

• Host machine turned off or has suffered a problem.
• WMI request blocked by machine or a firewall.

  Check the log for the machine on the Monitored servers page.

Raised when:

One of the following conditions applies continuously for longer than the time you specify:

• Problems with WMI
• File sharing issues

Configurable thresholds:

SQL Monitor cannot collect data from the host machine for longer than x  seconds/minutes/hours/days

Default settings:

Raised as Medium when SQL Monitor cannot collect data from the host machine for longer than 30 seconds

Type:

Continuous

Automatically updated from Active to Ended when data can be collected from the host machine again.

Possible causes:

• One of the required services (WMI or RPC) has been stopped.
• Remote file access permissions have changed or hidden administrative shares have been disabled.

Raised when:

SQL Monitor is unable to collect monitoring data from the host machine for longer than the time you specify, because the credentials supplied to connect to the machine are invalid or lack permissions.

Configurable thresholds:

Host machine cannot be contacted for longer than x seconds/minutes/hours/days

Default settings:

Raised as High when the host machine cannot be contacted due to an authentication failure for longer than 30 seconds

Type:

Continuous

Automatically updated from Active to Ended once the correct credentials are entered and authentication is confirmed.

Possible causes:

• Your user name or password has been changed.
• Your permissions have changed and are no longer sufficient.

Raised when:

One of the following conditions apply, depending on how you configure the alert:

• physical memory used is above a percentage threshold, OR
• physical memory available is less than a fixed value.

Configurable thresholds:

You can configure this alert in two ways:

• Used physical memory percentage, or
• Physical memory available (in MB or GB).

  Low physical memory has lasted longer than x seconds.

Default settings:

Alert is disabled by default

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when physical memory is above the lowest defined threshold for at least the specified duration.

Possible causes:

• SQL Server has been configured with insufficient memory.
• Page file space running low.
• Other processes consuming physical memory.
• Not enough RAM on server.

Note:

SQL Monitor only collects physical memory data at 15-second intervals:

• the minimum value for the duration is 15 seconds.
• when you configure the alert, change the duration value by 15 second increments.

Raised when:

Total processor utilization, averaged across all CPUs, is below a percentage threshold for longer than a specified duration.

Configurable thresholds:

Processor utilization less than a specified percentage.

Under-utilization has lasted longer than x seconds.

Default settings:

Alert is disabled by default

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when processor utilization is above the lowest defined threshold for at least the specified duration.

Possible causes:

Processor utilization is not as high as expected under normal operations: may indicate that SQL Server is not running normally or processing data - freeing up CPU.

Note:

SQL Monitor only collects processor utilization data at 15-second intervals:

• the minimum value for the duration is 15 seconds.
• when you configure the alert, change the duration value by 15 second increments.

Raised when:

Total processor utilization, averaged across all CPUs, is above a percentage threshold for longer than a specified duration.

Configurable thresholds:

Processor utilization above a specified percentage.

Utilization above this percentage has lasted longer than x seconds.

Default settings:

Raised as Medium when processor utilization is more than 90% for longer than 600 seconds

Type:

Continuous

Can have multiple thresholds applied and is automatically updated from Active to Ended when processor utilization is above the lowest defined threshold for at least the specified duration.

Possible causes:

• Other processes running on the server - check the System processes area of the raised alert.
• CPU-intensive SQL queries - if Profiler trace is turned on for the SQL Server, check the SQL statements in the SQL processes/Profiler trace area of the raised alert.

Note:

SQL Monitor only collects processor utilization data at 15-second intervals:

• the minimum value for the duration is 15 seconds.
• when you configure the alert, change the duration value by 15 second increments.

   

Raised when:

SQL Server Browser Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

   

Raised when:

SQL Server Integration Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.

Raised when:

SQL Server VSS Service status matches the status specified in the alert configuration.

Configurable thresholds:

Service status is one of the following:

• Stopped
• Stopped or paused
• Started
• Started or paused

Default settings:

Raised as Medium when service is Stopped

Type:

Continuous

Automatically updated from Active to Ended when the service status changes to a status other than that specified.

Possible causes:

• Service failed
• Service manually stopped or started

  Check the list of component services on the relevant Windows machine.