| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | monikerRange | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Use Performance Objects |
Use Performance Objects |
markingmyname |
maghan |
01/19/2017 |
sql |
ssms |
how-to |
|
= azuresqldb-mi-current || >= sql-server-2016 |
[!INCLUDE SQL Server SQL MI]
Important
On Azure SQL Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Managed Instance T-SQL differences from SQL Server for details.
[!INCLUDEssNoVersion] Agent includes performance objects and counters to monitor how the service is performing. These performance objects allow you to use Performance Monitor, a Windows tool, to identify what the [!INCLUDEssNoVersion] Agent service is doing in the background. For example, you can identify how many active jobs the [!INCLUDEssNoVersion] Agent service is currently running to identify those jobs that are blocked.
The [!INCLUDEssNoVersion] Agent service performance objects and counters exist for each instance of [!INCLUDEssNoVersion] that is installed on a computer. Performance objects are named according to the instance of [!INCLUDEssNoVersion] that each object represents.
The following table shows how the [!INCLUDEssNoVersion] Agent service performance objects are named:
| Instance type | Object name |
|---|---|
| Default | SQLAgent:object:counter |
| Named | SQLAgent$ *instance_name* :object:counter |
[!INCLUDEssNoVersion] includes the following performance objects for [!INCLUDEssNoVersion] Agent.
| Object name | Description |
|---|---|
| SQLAgent:Jobs | Performance information about jobs that have been started, success rates, and current status |
| SQLAgent:JobSteps | Status information about job steps |
| SQLAgent:Alerts | Information about number of alerts and notifications |
| SQLAgent:Statistics | General performance information |
Monitor and Tune for Performance
How to: Start System Monitor (Windows)