How to solve SQL Server alarms

How to solve SQL Server alarms

For specific solutions, refer to the following:

◆ Check whether you have used the latest SQL Server service pack. This is because many SQL Server warnings (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.

◆ Check whether the account of the SqlServerAgent service runs under the Domain User Group as a member. The LocalSystem account does not have the permission to access the network. Therefore, if you need to record events to application logs running on other Windows NT or Windows 2000 machines, or your jobs) cross-network resources are required, or you need to notify the operator via e-mail or pagers. In this case, you need to set the account of the SalServerAgent service to the Domain User Group) as a member.

◆ If none of the defined alarms are triggered, check whether the SqlServerAgent and EventLog services are running. If you want to trigger your defined alarms, these services must be enabled. Therefore, if these services are not running, run them.

◆ If an alert is not triggered, make sure it is enabled. The alarm can be 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.

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

6. Check SQL Server error logs, SQL Server Agent error logs, and Windows NT and Windows 2000 application logs for more details about Error Descriptions. Check carefully when an alarm fails, the date and time recorded in the SQL Server Error Log, SQL Server Agent error log, and Windows NT and Windows 2000 application logs, as well as the description of the error, can help you analyze the events that generate alerts for failure..

7. if the alarm is triggered but the operator does not receive any notification at this time, 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 an error % C.