FIX: Only One SQL Server Performance Condition Alert Is Treated As Active

Article translations Article translations
Article ID: 275145 - View products that this article applies to.
This article was previously published under Q275145
BUG #: 56180 (SQLBUG_70)
BUG #: 351829 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

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.

STATUS

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.

MORE INFORMATION

If you have a performance condition alert for Active transactions on the pubs database with the following properties:
Name Alert transaction
Type : SQL Server Performance condition alert
Object : SQLServer:Databases
Counter : Active Transactions
Instance : pubs
Alert 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 connection
Type : SQL Server Performance condition alert
Object : SQLServer:General statistics
Counter : User connections
Alert if counter : rise above 5
delay 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.

Properties

Article ID: 275145 - Last Review: March 14, 2006 - Revision: 4.2
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbbug kbfix KB275145

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com