SkillVaultskills Browse all 1,000+ skills

Debugging · Version 1.1.0 · Reviewed 2026-08-02

SQL Server Production Debug Specialist

Diagnose SQL Server production incident triage and SQL Server root-cause isolation with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Diagnoses production failures from runtime evidence instead of symptom matching in SQL Server using schema, actual plans, indexes, statistics, and workload settings and Query Store, wait statistics, memory grants, and blocking chains, with explicit attention to parameter-sensitive plans or oversized memory grants destabilizing concurrent workloads.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • SQL Server production incident triage
  • SQL Server root-cause isolation
  • SQL Server fix verification

How SQL Server Production Debug Specialist works

You provide

Schema, query plans, and the real access pattern

It inspects

Plan accuracy and lock behavior for SQL Server production incident triage

It decides

A SQL Server root-cause isolation change weighed against write cost

You verify

Re-measured plan with buffer reads and timing compared

What it checks first

SQL Server Production Debug Specialist diagnoses production failures from runtime evidence instead of symptom matching in SQL Server using schema, actual plans, indexes, statistics, and workload settings and Query Store, wait statistics, memory grants, and blocking chains, with explicit attention to parameter-sensitive plans or oversized memory grants destabilizing concurrent workloads. Use it when the work involves SQL Server production incident triage, SQL Server root-cause isolation, SQL Server fix verification.

  1. The actual query plan with real row counts, not the estimated plan or the query text alone.
  2. Whether the workload is read-heavy, write-heavy, or mixed, since the correct design differs sharply.
  3. Transaction boundaries and duration, because long transactions block vacuum and hold locks.
  4. Index coverage relative to both the filter and the sort, since satisfying one but not the other still costs a sort.
  5. Connection pool behavior, as pool exhaustion presents as database slowness while the database is idle.

Failure modes it recognizes

  • An index that serves the predicate but not the ordering, forcing a full sort for a small LIMIT.
  • A long-running transaction preventing vacuum and causing gradual bloat and plan degradation.
  • Implicit type casting on a join or filter column silently disabling index use.
  • Connection pool exhaustion from long-held connections, appearing as a database problem.
  • A write-heavy table with excessive indexes where insert cost dominates the workload.
  • Statistics stale after a bulk load, so the planner chooses a plan for a table size that no longer exists.

Answers it will reject

  • Adding an index per slow query until write amplification becomes the new bottleneck.
  • Tuning configuration parameters before examining the plan for the dominant query.
  • Interpreting `EXPLAIN` without `ANALYZE`, which reports estimates and proves nothing.
  • Increasing pool size to fix latency caused by lock contention, which adds waiters rather than capacity.

Decision rules it applies

  • Optimize the query that dominates total time, not the one that feels slowest in isolation.
  • Order composite index columns by equality first, then range or sort last.
  • Keep transactions short and never hold one open across an external call.
  • Create and drop indexes concurrently on live tables, accepting the longer build for the absent lock.

Evidence it asks for

  • `EXPLAIN (ANALYZE, BUFFERS)` to compare estimated with actual rows and attribute I/O.
  • Rank queries by cumulative execution time rather than by single-execution latency.
  • Monitor the oldest open transaction and lock wait counts as standing metrics.

The method inside

  1. Reconstruct the symptom timeline and define what healthy behavior would look like for SQL Server production incident triage.
  2. Rank hypotheses for SQL Server root-cause isolation by evidence, blast radius, and ability to explain every observed symptom.
  3. Run the cheapest discriminating check for SQL Server fix verification; update confidence only when evidence changes.
  4. Separate immediate stabilization, confirmed cause, contributing conditions, and prevention; finish with a reproducible verification.

Deliverables

  • SQL Server production incident triage assessment
  • SQL Server root-cause isolation decision and action plan
  • SQL Server fix verification verification checklist

Evidence requirements

  • Exact symptoms and timestamps
  • Reproduction conditions and recent changes
  • Logs, traces, metrics, code, or configuration

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the production debug specialist to our SQL Server system before the next production change. We can provide schema, actual plans, indexes, statistics, and workload settings; the main concern is parameter-sensitive plans or oversized memory grants destabilizing concurrent workloads.

Expected output

Start with Query Store, wait statistics, memory grants, and blocking chains and split the affected population before changing configuration. The leading hypothesis is parameter-sensitive plans or oversized memory grants destabilizing concurrent workloads. Run the smallest test that distinguishes that mechanism from dependency failure, preserve the evidence, and verify recovery against the original symptom.

Boundaries and compatibility

Ideal for

  • SQL Server production incident triage: produce a decision or artifact grounded in supplied evidence.
  • SQL Server root-cause isolation: produce a decision or artifact grounded in supplied evidence.
  • SQL Server fix verification: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Guessing a root cause from a symptom alone
  • Claiming a fix worked without test evidence

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.