Server Za Surf
|
|
Za Wczesnie $9.99 Za Wczesnie |
|
|
Anshur-Za $12.99 Anshur-Za |
|
|
Za morom $10 Za morom – Vetroplach |
|
|
Za poledne $10 Za poledne – Nerez |
|
|
Za sebou $10 Za sebou – Street69 |
Analyzing Performance With SQL Server Monitoring Counters
SQL server monitoring utilizes SQL server counters. They allow you to measure the various factors of SQL server performance. Gathering this data over a period of time lets you view past trends to learn how to optimize your server for the future. These counters can be utilized for specific metrics of your choice. Doing so will provide quick and easy ways to identify SQL server performance problems.
Discover more SQL Server monitoring tactics.
Below is a list of five common SQL Server counters to employ as part of your SQL Server optimization efforts.
1. Buffer Manager: Page Life Expectancy
The page life expectancy counter measures how long pages stay in the buffer cache. Their unit of measure is in seconds. The longer a page stays in memory the more likely SQL Server queries will not need to read from disk. As page life expectancy is increased so will the performance of the system.
2. Batch Requests/Second
The amount of batches a SQL server can get per second is measured by batch requests/per second. It shows the activity that a SQL server is currently processing. As the numbers grow, so do the number of query executions. SQL Server optimization requires periodic measurements to determine SQL Server performance over time.
3. SQL Compilations/Second
SQL compilations/second measures the number of times SQL Server compiles an execution plan per second. This procedure is very resource intensive and can hurt your SQL server performance. This measurement should be compared to batch requests/second to determine whether or not compilations are hurting performance.
4. Buffer Cache Hit Ratio
This ratio will show how many times SQL servers find data pages in their buffer cache when requested through a query. Performance improves as the number reaches closer to 100. Essentially it means that a SQL server was able to grab necessary data from memory and not from a disk.
Learn about the benefits of SQL Server optimization.
5. Lock Waits/Second
Sometimes SQL servers must lock the system resources to be able to handle the increased numbers of users using the system simultaneously. Lock waits/seconds is a measurement that counts how many times a SQL server couldn't retain a lock. Failure to retain a lock negatively impacts SQL Server performance. In a perfect world this number would be 0. As numbers stretch further from 0 performance will decrease.