Databases Reference
In-Depth Information
However you choose to look at locking within SQL Server, being as familiar with the architecture as you
can will yield great benefits when a high-priority problem occurs and you don't have to stop and read
up on how it all works. SQL Server 2005 Books Online is a great resource to continue your reading on
the subject.
Summary
This chapter has described the concept behind a SQL Server wait and covered the architecture to
provide an understanding of why they can be useful to monitor. It detailed the different ways that wait
information can be gathered, showed you how to interpret the information, and looked at a free
performance data warehouse application called DMVStats, which has been released by Microsoft. The
final part of the chapter focused on locking and blocking within SQL Server. It described why locking is
employed, how it works, how to view locking with DMVs, and what methods there are to monitor and
troubleshoot locking over an extended period.
Now that you know how to find and monitor for blocking problems you can turn to Chapter 9 for details
on how to minimize and resolve blocking through sensible coding strategies or continue with the next
chapter, which maintains the theme of troubleshooting tools and techniques with a closer look at SQL
Profiler.
Search WWH ::
Custom Search