| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Cpu_busy
|
The percentage of time for which the server's CPU was engaged in processing requests to the server |
Percent
|
A high value of this measure indicates a heavy load on the server. If this value comes close to 100%, it could indicate a probable delay in the processing of subsequent requests to the server. The detailed diagnosis measures associated with the Background_processes measure of the MsSqlSysProcsTest will help you identify the processes that are consuming excessive CPU resources.
|
| IO_busy
|
The percentage of time for which the server was engaged in performing input/output operations |
Percent
|
|
| Idle
|
The percentage of time for which the server was idle |
Percent
|
A low value of this measure is indicative of high CPU utilization. The detailed diagnosis measures associated with the Background_processes measure of the MsSqlSysProcsTest will help you identify the processes that are consuming excessive CPU resources. Similarly, the detailed measures of the Sleeping_processes measure (mapped to the MsSqlSysProcsTest) will reveal the duration for which every process executing on the server had remained idle.
|
| Packets_received
|
The rate at which input packets were read by the SQL server |
Pkts/Sec
|
This measure is an indicator of server health.
|
| Packets_sent
|
The rate at which output packets were read by the SQL server |
Pkts/Sec
|
This measure is an indicator of server health.
|
| Packet_errors
|
The rate at which packet errors occurred |
Errors/Sec
|
Ideally, this value should be 0.
|
| Disk_reads
|
The rate of disk reads performed by the Microsoft SQL server |
Reads/Sec
|
The value of this measure should be kept at a minimum, as disk reads are expensive operations. Ideally, data reads should be performed from the server cache and not directly from the disk. To ensure effective cache usage, allocate adequate memory to the Microsoft SQL server.
|
| Disk_writes
|
The rate of disk writes performed by the Microsoft SQL server |
Writes/Sec
|
The value of this measure should be kept at a minimum, as disk writes are expensive operations. Ideally, data should be written to the data cache and not directly to the disk. To ensure effective cache usage, allocate adequate memory to the Microsoft SQL server.
|
| Disk_io_errors
|
The rate of errors encountered by the Microsoft SQL server while reading and writing |
Errors/Sec
|
Disk read/write errors are normally caused by the following reasons:
- Semaphore contention
- Excessive disk space consumption
|