PerformanceCondition Property
Esse recurso será removido em uma versão futura do Microsoft SQL Server. Evite usar esse recurso em desenvolvimentos novos e planeje modificar os aplicativos que atualmente o utilizam.
The PerformanceCondition property specifies a Microsoft Windows Performance Monitor counter, a comparison operator and value, and enables raising a Microsoft® SQL Server™ 2000 Agent alert based on system activity.
Sintaxe
object
.PerformanceCondition [=value]
Parts
object
Expression that evaluates to an object in the Applies To listvalue
String that specifies a Windows Performance Monitor object, counter, and instance as described in Remarks
Data Type
String
Modifiable
Read/write
Prototype (C/C++)
HRESULT GetPerformanceCondition(SQLDMO_LPBSTR pRetVal)
HRESULT SetPerformanceCondition(SQLDMO_LPCSTR NewValue)
Observação |
---|
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 using SysFreeString. |
Comentários
When setting the PerformanceCondition property, value uses the syntax:
ObjectName
|
CounterName
|
Instance
|
ComparisonOp
|
CompValue
Part |
Description |
---|---|
ObjectName |
Name of a 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 relational operators =, >, 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 (1,000 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 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 Using SQL Server Objects.