SQLServer: Buffer Manager - Buffer cache hit ratio
The percentage of pages that were found in the memory. Higher the value the better. Preferred around the 90% mark. This included the availability of the procedure and the data cache in the system.
SQLServer: General Statistics - User Connections
The number of users currently connected to the SQL Server.
SQLServer:Access Methods - Full Scans / sec
Value greater than 1 or 2 indicates that we are having table / Index page scans. We need to analyze how this can be avoided.
SQLServer:Access Methods - Table Lock Escalations/sec
This gives us the number of times a table lock was asked for in a second. A high number needs a revisit to the query and the indexes on the table.
Processor - %Processor Time
The percentage of time the processor spent executing a non-idle thread. This value is subtracted from the time the processor was idle 100 percent. This is an indicator to the overall CPU utilization in the system.
Processor - %Interrupt Time
The percentage of time the processor spent servicing hardware interrupts. This can be any activity on the server machine. This needs to be 0 while our testing process.
Processor - Processor Queue Length
This counter indicates the number of threads that are waiting in the processor queue. It can be also interpreted as the number of threads that are waiting to be run by the processor. If this value is greater than the number of processor then we have a CPU bottleneck in the system.
Processor - Context Switches/sec
A typical context switch occurs when the OS or the application is forced to change the executing thread on one processor to another thread executed on another processor. This value has to be as small as possible. Context switches are not avoidable in multi-processor machines. Hence any value below 10000 is fine.
PhysicalDisk - %Disk Read Time
Time spent by the disk for read operation. We can have disk by disk analysis also to narrow down any read IO bottlenecks.
PhysicalDisk - %Disk Write Time
Time spent by the disk for write operation. We can have disk by disk analysis also to narrow down any write IO bottlenecks.
PhysicalDisk - Avg. Disk Queue Length
Average number of requests that waited for the read and write requests in the particular disk. A high value suggests we have an IO bottleneck.
Memory - Page Faults/sec
Total number of faulted pages handled by the processor per second. This value needs to as small as possible.
Memory - Pages/sec
The number of pages written to disk or from disk to resolve page faults. This would be the sum of page reads/sec and page writes/sec counter.
