The Processes panel provides access to, and information about, the following:
Component | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Total |
Shows the total number of SQL Server sessions (SPIDs). It includes both user and system sessions. | ||||||||
System |
Shows the total number of current SQL Server System sessions (SPIDs). This includes any sessions from SQL Server system processes such as the Checkpoint, LogWriter and LazyWriter processes etc., as well as various SQL Server Agent system processes (Alert Engine, Email Logger etc.). | ||||||||
User |
Shows the total number of current User (non-system) sessions, excluding SQL Server Agent sessions. | ||||||||
Blocked Processes |
Shows the number of sessions that are waiting on locks held by others. | ||||||||
Virtualization Overhead |
In a virtual environment the physical CPU of a host is shared by virtual machines and the hypervisor. Multiple processes may want to use the physical CPU of the host at the same time. The virtual machines may have to wait to be scheduled on a CPU.
| ||||||||
CPU Usage |
Represents the total amount of CPU being used on the Windows server. It includes CPU consumed by all Windows processes, not just SQL Server. This component spins faster as CPU demands increase. |
Component | Description |
---|---|
Logical Read/s |
This flow from the Memory panel to the Processes panel shows the rate at which pages in the Buffer Cache are being referenced by SQL connections (logical page reads). Normally, the majority of Logical Reads will be satisfied from the cache, but if the required page is not already there, it will be read from disk. |
Compiles/s |
This flow from the Processes panel to the Memory panel shows the rate of SQL compilations and re-compilations. All SQL statements need to be compiled by SQL Server before they are executed. Compiling is the process by which SQL Server converts the SQL statement into an executable query plan. Under certain circumstances, SQL Server will re-compile SQL statements. Recompiling can consume a large amount of CPU, and can degrade performance. Sound coding practices, such as using Stored Procedures and parameterizing queries, can help to reduce recompiles. |
© 2022 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy