Chapter 13. Block and deadlock analysis

If only one or two users needed to get to your data, then locking and blocking wouldn’t be necessary, but there wouldn’t be very much point to having SQL Server, either! As it is, concurrent-access database systems like SQL Server implement locking to help ensure individual users don’t overly impact one another when they’re all accessing the same data. In this chapter, we’ll look at what locks do, how they work, and how they can negatively impact system performance. I’ll be focusing on helping you gather evidence of poorly written or slow-running queries, so that you can work with a developer or vendor to help improve performance.

13.1. What’s locking and blocking?

Imagine a bunch of people gathered ...

Get Learn SQL Server Administration in a Month of Lunches now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.