1. Check whether you have used the latest SQL Server service pack.
This is because many Alerts vulnerabilities have been fixed in the latest SQL Server service pack. Make sure that the latest SQL Server service pack patch package has been installed in your system.
2. Check whether the account of the SqlServerAgent service runs as a member in the Domain User Group LocalSystem account. It has no permission to access the network. Therefore, if you need to record events on application logs running on Windows NT or Windows 2000 machines, or your jobs need cross-network resources, or you need to notify the operator via e-mail or pagers. At this time, you need to set the account of the SalServerAgent service under the Domain User Group as its member.
3. If the defined alarms are not triggered, check whether the SqlServerAgent and EventLog services are running. If you need to trigger the alarms you have defined, these services must be enabled. Therefore, if these services are not running, run them.
4. If an alarm is not triggered, make sure that the alarm is enabled or disabled. To check whether an alarm is enabled, perform the following steps:
1) Run SQL Server Enterprise Manager
2) open the server group and then open a server
3) open Management and then enable SQL Server Agent.
4) double-click the appropriate alarm to check whether the alarm is enabled.
5) Check the historical alarm value to determine the date and time when the alarm was last executed
To check the historical value of an alarm, you should do the following:
1) Run SQL Server Enterprise Manager
2) open the server group and then open a server
3) open Management and then enable SQL Server Agent.
4) double-click the appropriate alarm to view the historical alarm value.
6. Check the counter value maintained every 20 seconds.
Because the SQL Server Agent maintains a performance counter every 20 seconds, if you find that this performance counter is only maintained for a few seconds (less than 20 seconds, it is very likely that your alarm will not be triggered.
7. check the SQL Server error log, SQL Server Agent error logs and Windows NT and Windows 2000 application logs for more details about error descriptions. Check carefully when an alert failure event is generated, error logs recorded on SQL Server, the SQL Server Agent error log, 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 alarm failure event.
8. if the alarm is triggered but the operator does not receive any notification at this time, try to manually use "e-mail ", "pager" or "net send" is used to send information to the operator. In many cases, you enter an error % C
