The PerformanceCondition property specifies a Windows NT Performance Monitor counter, a comparison operator and value, and enables raising a SQL Server Agent alert based on system activity.
object.PerformanceCondition [= value]
| Part | Description |
|---|---|
| object | Expression that evaluates to an object in the Applies To list |
| value | String specifying a Windows NT Performance Monitor object, counter, and instance as described in Remarks |
When setting the PerformanceCondition property, value uses the syntax:
ObjectName|CounterName|Instance|ComparisonOp|CompValue
| Part | Description |
|---|---|
| ObjectName | Name of monitored Microsoft® SQL Server™ object |
| CounterName | Name of a counter exposed by the object |
| Instance | Name of an instance of the counter |
| ComparisonOp | One of the symbols =, >, or < |
| CompValue | Numeric value compared |
For example, to create an alert raised when the average wait time for an extent lock rises above 1 second (1000 milliseconds), set the PerformanceCondition property using the string:
SQLServer:Locks|Average Wait Time (ms)|Extent|>|1000
Many SQL Server Performance Monitor counters do not define instance parameters. When an instance parameter is not applicable, indicate that no instance is selected by using an empty Instance part in the value string, as in:
SQLServer:Access Methods|Page Splits/sec||>|50
For more information about SQL Server objects exposing Performance Monitor counters, see SQL Server Objects and Counters.
String
Read/write
HRESULT GetPerformanceCondition(SQLDMO_LPBSTR pRetVal)
HRESULT SetPerformanceCondition(SQLDMO_LPCSTR NewValue)
Note SQL-DMO strings are always returned as OLE BSTR objects. A C/C++ application obtains a reference to the string. The application must release the reference by using SysFreeString.