Database Bottleneck Diagnosis · Workshop
Bottleneck Signals Lab
Correlate wait stats, buffer churn, and plan regressions to decide whether the fix belongs in SQL, app batching, or infra.
- Duration
- 2 weeks · intensive weekend labs
- Skill focus
- Intermediate
- Platform lens
- SQL Server
- Tuition (informational)
- ₩720,000
Overview
Mid-level engineers often oscillate between blaming the database and blaming the network. This lab gives you a repeatable classification worksheet so you can brief stakeholders with evidence. Scenarios include sudden plan flips after statistics updates and latch storms from oversized batch inserts.
What is included
- Signal triage worksheet (PDF)
- Three guided incidents with hidden twists
- Coach feedback on your written postmortem
- Channel for follow-up questions for 30 days
Outcomes
- Classify an incident into SQL vs app vs infra buckets
- Draft a concise incident note with evidence links
- Pick the next measurement before touching code
Primary coach
Elena Varga
Runs cohort kickoffs and keeps enterprise workshops aligned with internal release cadences.
FAQ
Do I need Extended Events experience?
Helpful but not required—we start from canned captures and explain fields in plain language.
Linux hosts?
Labs assume Windows-friendly tooling paths; Linux equivalents are linked as optional reading.
What is out of scope?
We do not broker vendor support tickets or escalate to Microsoft CSS on your behalf.
Experience notes
-
Bottleneck Signals Lab forced us to document waits before jumping to index changes—small habit, big calm.
-
Short on time for the weekend block, but the async incident writeups still felt worthwhile.
Tuition is informational on this static preview. Enrollment teams confirm availability, tax treatment, and any employer procurement paperwork steps. See Returns & Refunds for eligibility framing.