How the SQL Server alert should resolve

Q: How should SQL Server alert problems be resolved?

Answer: Please refer to the specific solution:

Check to see if you are using the latest SQL Server service pack. Because many SQL Server usage warnings have been patched in the latest SQL Server Service Pack (Alerts) Vulnerabilities. You should make sure that you have the latest SQL Server Service Pack patches installed in your system.

Check to see if the account for the SQLServerAgent service runs under the domain user group as a member. The LocalSystem account does not have access to the network, so if you need to log events in other running Windows On an NT or Windows 2000 machine Application log, 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 Salserveragent service account in the domain user group (Domain User Group) as its members.

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.

If an alert is not triggered, make sure they are enabled. Alerts can be enabled or disabled, and to check if an alert is enabled, you should do the following:

1. Run SQL Server Enterprise Manager

2, please open the server group, and then open a server

3, please open the management (Management), and then open the 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. Run SQL Server Enterprise Manager

2, please open the server group, and then open a server

3, please open the management (Management), and then open the SQL Server Agent

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

5, check every 20 seconds to maintain the counter value

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).

6. Check the SQL Server error log, the SQL Server Agent error log, and the Windows NT and Windows 2000 application logs for more detailed information about the error description. Check carefully for checks when an alert failure event occurs, it is logged in the SQL 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.

7. If the alarm is triggered, but the operator does not receive any notification, please try to manually use "e-mail", "pager" or use "net send" to send the information to the operator. In many cases, you may have entered a wrong%c.