Scribd
Upload
20 views

Common Perfomance Counter To Measure For SQL Server (There Are Lots More)

This document outlines common performance counters to monitor for SQL Server, including CPU usage, memory usage, disk performance, network traffic, and locks/blocking. It recommends keeping the CPU usage under 90%, page life expectancy above 300 seconds, buffer cache hit ratio close to 100%, and minimizing locks, blocking, and page splits. Disk read/write times should be under 8ms and 2ms respectively. Network traffic counters do not have specific thresholds.

Uploaded by

Djebrani Aziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views

Common Perfomance Counter To Measure For SQL Server (There Are Lots More)

This document outlines common performance counters to monitor for SQL Server, including CPU usage, memory usage, disk performance, network traffic, and locks/blocking. It recommends keeping the CPU usage under 90%, page life expectancy above 300 seconds, buffer cache hit ratio close to 100%, and minimizing locks, blocking, and page splits. Disk read/write times should be under 8ms and 2ms respectively. Network traffic counters do not have specific thresholds.

Uploaded by

Djebrani Aziz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

COMMON PERFOMANCE COUNTER TO MEASURE FOR

SQL SERVER (THERE ARE LOTS MORE)

CPU:

When we observe a high rate of CPU usage that may indicate

the need to either upgrade or add a processors.

Processor: % Processor Time

This counter monitors the amount of time the CPU

spends executing a thread. A measurement of 80 to 90

percent may indicate the need to upgrade your CPU or

add more processors.

Processor – Processor Queue Length

This counter indicates the number of threads that are

waiting in the processor queue. If this value is greater

than the number of processor then we have a CPU issue


MEMORY:

The Available Bytes

Indicates how many bytes of memory are currently

available for use by processes.

Low values for the Available Bytes counter can indicates

an overall shortage of memory on the computer or that

an application is not releasing memory.

The Pages/sec

Indicates the number of pages that either were

retrieved from disk due to hard page faults or written to

disk to free space in the working set due to page faults.

A high rate for the Pages/sec counter could indicate

excessive paging.
SQLServer: Buffer Manager: Buffer cache hit ratio

This represents how often SQL Server is able to find

data pages in its buffer cache. The higher this number

the better, because it means SQL Server was able to get

data for queries out of memory instead of reading from

disk. Keep close to 100 as possible.

SQLServer: Buffer Manager: Page life expectancy

The page life expectancy counter measures how long

pages stay in the buffer cache in seconds. Below 300 (or

5 minutes) means you might need additional memory.

SQLServer: SQL Statistics: Batch Requests/Sec

Batch Requests/Sec measures the number of batches

SQL Server is receiving per second. A good indicator of

how much activity is being processed by your SQL


Server box. The higher the number, the more queries

are being executed on your box.

SQLServer: SQL Statistics: SQL Compilations/Sec

The SQL Compilations/Sec measure the number of

times SQL Server compiles an execution plan per

second. Compiling an execution plan is a resource-

intensive operation. Ideally you want to have one

compile per every 10 batch requests.

SQLServer: SQL Statistics: SQL Re-Compilations/Sec

When the execution plan is modified, SQL Server will re-

compile it. The Re-compilations/Sec counter measures

the number of time a re-compile event was triggered

per second. Minimize the number of re-compiles.

SQLServer: General Statistics: User Connections


The user connections counter identifies the number of

different users that are connected to SQL Server

SQLServer: Locks: Lock Waits / Sec: _Total

Lock waits per second counter tracks the number of

times per second that SQL Server is not able to retain a

lock right away for a resource. Ideally you don't want

any request to wait for a lock. Therefore you want to

keep this counter at zero, or close to zero at all times.

SQLServer: Access Methods: Page Splits / Sec

This counter measures the number of times SQL Server

had to split a page when updating or inserting data per

second. Ideally this counter should be less than 20% of

the batch requests per second.

SQLServer: General Statistic: Processes Block

The processes blocked counter identifies the number of

blocked processes. When one process is blocking


another process, the blocked process cannot move

forward with its execution plan until the resource that is

causing it to wait is freed up. Ideally you don't want to

see any blocked processes. When processes are being

blocked you should investigate.

DISK:

A Logical disk is a disk partition, while a physical disk is the

complete physical disk with all partitions created on it.

Average Disk sec/Read

The Average Disk sec/Read metric. The shorter the


time needed to read or write data, the faster the
system

Less that 8ms = good

Average Disk sec/Write

Average Disk sec/Write. The average time in seconds needed


to write data to disk

Less that 2ms = good


NETWORK

A client who accesses the server over a slow or saturated


network will encounter delays

Network Bytes Received/sec

The Network Bytes Received/sec counter shows the byte


rate at which information is received over each network
adapter.

There is no specific threshold value.

Network Bytes Sent/sec

Similar to the Network Bytes Received/sec counter, the


Network Bytes Sent/sec counter shows the rate at which
bytes are sent over each network adapter.

There is no specific threshold value.

You might also like