Troubleshoot problems with SQL Server alerts

If you are having problems using the alerts in Microsoft SQL Server (Alerts), please check this article for possible solutions.

1. Check to see if you are using the latest SQL Server Service pack

This is because many SQL Server usage warnings (Alerts) vulnerabilities have been patched in the latest SQL Server service pack. You should make sure that you have the latest SQL Server Service Pack patches installed in your system.

2. Check that the account for the SQLServerAgent service is running under the domain user group as a member

LocalSystem account It does not have permission to access the network. So, if you need to record the event on another application log that runs on Windows NT or Windows 2000 machines, or if your job requires resources across the network, or you need to notify the operator via e-mail or pagers, You will need to set the account for the Salserveragent service to be a member of the domain user group.

3. Check that the SQLServerAgent and EventLog services are running if the defined alerts are not triggered

If you need to let your defined alerts be triggered, these services must be turned on. So, if these services are not running, run them.

4. If an alert is not triggered, make sure that it is enabled

Alerts can be enabled or disabled, and in order to check whether an alert is enabled, you should do the following steps:

1. Running SQL Server Enterprise Manager

2. Please open the server group and open a server

3. Please open management (Management) and then open SQL Server Agent

4. Double-click the appropriate alert to see if this alert is enabled

5. Check the history value of the alert to determine the date and time the alert last worked

To check the historical value of an alert, you should do the following things:

1. Running SQL Server Enterprise Manager

2. Please open the server group and open a server