Dynamic Values in Current Activity Sub Screen

Buffer lookups per SQL batch

This counter represents the number of buffer pages that are requested in average per SQL batch. This value gives a good hint on the load of your SQL activity. In a BW system, for example this value is much higher than in an OLTP system.

Page reads / Readahead pages

This value reflects the ratio between number of pages read and the number of pages, which were read via Readahead.

Latch wait time per page request

This value shows how long in average a latch was set for a buffer page while waiting for the page being read from disk into the buffer.

Wait time per log write

This value is the average waiting time for the system until a page is written to the log.

IOStall per request

This value shows the average wait time for an I/O request. This includes read and write operations although the read operations dominate the wait time (most writes are asynchronous writes).

Physical server reads/sec

Number of physical reads from disk on a per-second basis (floating average). The value represents the number of reads for the whole server, not just the current database. Reads include all server activity.

Physical server writes/sec

Number of physical writes to disk on a per-second basis (floating average). The value represents the number of writes for the whole server, not just the current database. Writes include all server activity.

Lazy write/sec

Number of buffers written by the buffer manager's Lazy Writer. The Lazy Writer is a system process whose task is to write dirty buffers to disk when I/O activity is low. The goal of the Lazy Writer is to minimize the time needed by checkpoints to write dirty data pages to disk.

Log flushes

Number of disk flushes of the log.

Full table/index scans/sec

Number of full table or index scans. These scans can be either base-table or full-index scans. Value is displayed on a per-second basis.

Index range scans/sec

Number of qualified range scans through indexes. This number represents logical, as opposed to physical, access. Value is displayed on a per-second basis.

Index searches/sec

Number of index searches. Index searches are used to start range scans and single index record fetches. Value is displayed on a per-second basis.

Probe scans/sec

Number of probe scans that occur in a database. Probe scans are used to find rows in an index or base table directly. Value is displayed on a per-second basis.

CPU busy

Total number of seconds that the CPUs have been running SQL Server threads.

Each CPU counts separately. For example, if during two seconds, three CPUs are used, CPU busy is six.

CPU idle

Total number of seconds that the CPUs in SQL Server were not running SQL Server threads. For this time, the CPUs may not have been strictly idle, as they may have been used for SAP work processes.

IO busy

Shows the CPU time that was used by all available CPUs for I/O operations issued by SQL Server.

SQL batches

Number of SQL batches sent to the MS SQL Server.

Transactions

Number of transactions processed by the MS SQL Server.