This monitor tracks the performance of the queries that select Alerts matching the subscription criteria. If these queries are too slow it could result in delay of notifications sent out by the Notification subsystem.

The Alert queries can slow down usually because the Query processor in SQL Database is overloaded. IT is possible that the Operations database is under heavy load. If the alert query is complex it can slow down processing of the query.

Notification subsystem is taking a long time to generate notification messages. This is due to slowing down of the query processing used to match alert criteria presented in the subscription against the alerts in the Operations database.

• Note the high and low watermark information associated with Notification subsystem. These indicate the extents of the Alerts data in the Operations database that is being processed.

• Verify that the SQL query engine is not overloaded with many queries.

• Check the subscriptions in the Management group. If there are any subscriptions that have complex queries associated with it they can slow down the generation of all notifications. See if you can simplify the criteria for the alert.

• You may have too many subscriptions. Check if you can disable or delete unnecessary subscriptions.

• The computer hosting the Operations Database may not have sufficient resources. Diagnose the resources – hardware and software that are being over utilized. Adding more resources could ease the load.

• Many alerts may be getting generated in the system as a result of the alert storm. Turn off notification while Alerts can be tuned.

• Inspect the messages in the Operations Manager event log. Other indications of problems in the system may direct you to further diagnostic steps.