This paper approaches the complex area of Microsoft® SQL Server™ performance tuning using a methodology called Waits and Queues. By using this methodology one can identify the best opportunities to improve performance, the so called “biggest bang for the buck”. These performance improvements are likely to have a significant return on the performance tuning time investment. The methodology helps identify the areas of slow performance by looking at the problem from two directions. You, or another troubleshooter, can use this to pinpoint problem areas by correlating data from two sources: Waits and Queues. An analysis of Waits indicates where SQL Server is spending lots of time waiting. In addition, the biggest waits point out the most important or relevant Queues (that is, Performance Monitor counters and other data) for this workload. The cross validation of the waits analysis enables us to eliminate all except the most significant performance counters, and provides a strong indication of pressure on specific resources.
For more information, please refer to the SQL Server 2005 Waits and Queues whitepaper.
Today I witnessed a performance load test against a 16 proc 64-bit SQL Server instance. During the first
Introduction: The Classic Protocol, Amended Introduction My customers are often surprised to learn about
Preamble For those of you who are already facile with SQL Server wait stats, there’s nothing new here.
There are several dynamic management objects (DMOs) that I use on an ongoing basis in performance tuning
The whitepaper SQL Server 2005 Waits and Queues describes a methodology called Waits and Queues. By using
Pingback from Performance audit: Wait stats « A Data Professional's Blog
If you don’t know where you’ve been, how can you expect to know where you are going.
Pingback from If You Don’t Know Where You’ve Been… « Strate SQL
Pingback from Twitter Trackbacks for SQL Server 2005 Waits and Queues - Whitepapers [sqlcat.com] on Topsy.com
Pingback from Wait Stat Categories | Strate SQL
A few weeks ago I posted a job that I use to track wait stats in the DBA database that I bring to a number
I worked with a team of folks brought together by Quest software, and we presented multiple sessions
Pingback from Index Black Ops Part 2 – Page IO Latch, Page Latch | Strate SQL
Pingback from Slow DB Performance. Seems to be memory related.