SSMS Tips and Tricks 4-12: Avoiding deadlocks when working interactively
Several times, I’ve seen situations where a user who’s working interactively in SSMS ends up causing deadlocks and causing issues for an application that’s in use. This is even more likely for users who hold locks for long periods of time, and who work directly with production systems.
At best, they might just cause an application to hang. At worst, they might cause a poorly-designed application to terminate.
Why would a user hold locks for a long time? Many users work in what’s called chained mode, where they automatically start a transaction when they make any sort of update. Some other database engines default to that behavior, but you can choose that as a session option in SQL Server as well.
2025-11-15
