Troubleshoot problems with SQL Server alerts

server| solve the problem 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 as a member under the domain user group 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. If the defined alerts are not triggered, check that the SQLServerAgent and EventLog services are running 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 the alert is enabled or disabled and that you should do the following to check if an alert is enabled:

1 Running SQL Server Enterprise Manager

2 Open a server group, and then open a server

3 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 historical 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 Open a server group, and then open a server

3 Open Management (Management), and then open SQL Server Agent

4 Double-click the appropriate alert to view the alert's historical value

6. Check the counter value maintained every 20 seconds

Because the SQL Server Agent maintains a performance counter every 20 seconds, it is highly likely that your alert will not be triggered if the performance counter is found to be maintained only for a few seconds (less than 20 seconds).

7. Check the SQL Server error log, SQL Server Agent error log, and Windows NT and Windows 2000 application logs for more detailed information about the error description The check is logged in the SQL when an alert failure event occurs The server error log, the SQL Server Agent error log, and the date and time in the Windows NT and Windows 2000 application logs, and the description of the error can help you analyze the cause of the alert failure event.

8. If the alert is triggered, but the operator does not receive any notification at this time, try to manually use "e-mail", "pager", or send the message to the operator using "net send" in many cases, you have entered a mistake%c