Get SQL Server session Lock info quickly скачать в хорошем качестве

Get SQL Server session Lock info quickly

In this video, we walk through how SQL Server locking works and, more importantly, how to analyze locks when your system is experiencing blocking. Instead of diving deep into every lock type, the focus is on identifying who is blocking whom and how to quickly pinpoint the root cause. We start by creating a transaction that intentionally holds a table lock, then run multiple sessions against it to simulate blocking. Using sp_sessions, we can immediately see the lead blocker and the sessions waiting behind it. These waits are lock waits, and understanding them is key to diagnosing performance issues. While SQL Server’s built‑in sp_lock can show lock details, it often requires manual conversion of IDs to database and object names. To make this easier, the video introduces a custom function, fn_GetLockInfo, which returns readable lock information—including database names, object names, and lock types—without any extra decoding. Because it’s a SELECT‑based function, you can filter it with WHERE clauses, target a specific database, or analyze a single session ID. This makes it much faster to understand what’s happening, especially when multiple sessions are hitting the same table or when one session is holding an exclusive lock that’s blocking others. The video also shows how to look up unfamiliar lock types (like intent locks) using your preferred search engine—or Copilot—to understand what they mean. The fn_GetLockInfo function is available for free on GitHub, and viewers are encouraged to download it, modify it as needed, and report any bugs. https://github.com/TheFriendlyDBA/SkillByP...