Learn why deadlocks confuse even seasoned developers and DBAs
If anyone tells you deadlocks are easy to solve, they’re probably drunk.
It’s time to talk about deadlocks.
I want you to pretend for a moment that you are a consultant
If you are already a consultant, well, it’s gonna be really easy for you.
Let’s say that you are a consultant, and you’ve got a client who comes to you and says:
I’m having this problem with deadlocks and I need your help figuring out what the heck is going on and how to keep these things from coming back.
If you are like most of us…
When you are presented with a deadlock, or even when you just hear the word, you are kinda like ah, get this sort of cold, creepy feeling.
There are many ways to get information about deadlocks in SQL Server, but they produce a lot of info and not all of them give you the right information you need to actually solve the problem.
You don’t have to be creeped out by this!
I’m going to show you the right information to collect, how to step through it and a couple of different techniques that I want you to consider first to see hey, is there an easy way to prevent this deadlock from happening.
Let’s take a look at deadlocks in SQL Server live in our demo.