The SQL Processes panel provides access to, and information about, the following:
|
|
|
Shows the total number of SQL Server sessions (SPIDs). It includes both user and system sessions. 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.). Shows the total number of current User (non-system) sessions, excluding SQL Server Agent sessions. Shows the number of sessions that are waiting on locks held by others. The Virtualization Overhead gauge shows the percentage of CPU that is unavailable to this virtual machine because it is being consumed either by other virtual machines or by VMware itself. In a virtual environment, the physical CPU of a host is shared by virtual machines and the VMware Hypervisor. This means there can be multiple processes wanting to use the physical CPU of the host at the same time. The result is that virtual machines may be ready to run but have to wait to be scheduled on a CPU. Vmware call this “ready time”. The Virtualization Overhead gauge shows the amount of ready time as a percentage of the theoretical maximum CPU available to the virtual machine. See "Configure the Virtualization Overhead Guage" (page 1) for more information. Represents the total amount of CPU being used on the machine being diagnosed. It includes CPU consumed by all Windows processes, not just SQL Server. This component spins faster as CPU demands increase. This flow from the SQL Memory panel to the SQL 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. This flow from the SQL Processes panel to the SQL 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. |
Total