When you create two or more SQL Server Performance Condition alerts, only one alert is treated as active although all the alerts are enabled. If you have two SQL Server Performance Condition alerts, the second alert is activated as soon as you edit the first one. Editing includes resetting the count or changing the conditions. The first alert then becomes deactivated.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
If you have a performance condition alert for Active transactions on the pubs database with the following properties:
Name Alert transactionType : SQL Server Performance condition alertObject : SQLServer:DatabasesCounter : Active TransactionsInstance : pubsAlert if counter : rise above 1 Delay between responses : 1 seconds
The alert works as intended and the count value in SQL Server Enterprise Manager is updated as the conditions are met.
Now, if another alert is created you get the following conditions:
Name: Alert connectionType : SQL Server Performance condition alertObject : SQLServer:General statisticsCounter : User connectionsAlert if counter : rise above 5delay between responses : 1 seconds
The new alert count is 0 even if you hit the alert condition multiple times.
If you modify the first alert "Alert Transaction" in any way, for example by editing the alert or resetting the count, the second alert "Alert Connection" is activated and the first alert is no longer active.