MKsql server / problems / blocking
Blocking is usually the first symptom people notice, not the first cause they prove.
This page is for the stage where the estate feels slow or stuck, several sessions are waiting, and the team still needs the quickest path from symptom to real blocker. It should get you to the right guide or the right help path fast, without pretending one DMV screenshot is a diagnosis.
Related
Use the SQL Server blocking guide for the deeper concurrency review, the SQL Server waits guide when the signal is still broad, the SQL Server deadlocks guide if the problem is already becoming cyclical, and SQL Server performance review when the issue is already live enough that the team needs sharper diagnosis now.
What it usually looks like
Common cause classes
Safe first checks
Why this page exists
People usually land here because something is already hurting: timeouts are stacking up, sessions are waiting, or one bad transaction is slowing far more work than it should. At that point the useful question is not “teach me everything about locks.” It is “what should we prove first so we stop guessing?”
That is why this page stays narrow. Blocking can come from transaction scope, access paths, schedule collisions, reporting habits, or maintenance work landing badly. The first job is to find the blocker, connect it to the real workload story, and decide whether this is mainly a blocking problem, a waits problem, or a broader performance review.
Best deeper pages
Longer review of blocking chains, transaction scope, access paths, workload timing, and production triage.
Best first read if the pattern is still broad and the waits story needs reading before you start naming the root cause.
Move to this if the contention is already escalating into cycles, victims, or retry-driven application errors.
Keep this nearby if weak evidence is the bigger blocker and the team still cannot prove how often the pattern repeats.
When outside help makes sense
This review fits once blocking is already hurting real work, the root cause is still unclear after the first checks, or the team needs diagnosis tied to workload behavior instead of generic tuning slogans.
Blocking, deadlocks, or slowness are hurting real work.
The root cause is still unclear after initial checks.
The team needs diagnosis tied to workload behavior, not generic tuning slogans.
Next step
If blocking is already hurting work, use SQL Server performance review or go straight to contact with what users are seeing, when it happens, and whether you already know the head blocker.
If you need the longer technical path first, start with the SQL Server blocking guide.
If the symptom is still broader than blocking alone, the better next page may be SQL Server slow performance.