troubleshoot-microsoft-sql-server

Troubleshoots Microsoft SQL Server incidents by analyzing Netdata mssql.* health signals for root causes.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-microsoft-sql-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-microsoft-sql-server
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-microsoft-sql-server
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-microsoft-sql-server

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Troubleshooting Microsoft SQL Server incidents that present as log full events, memory pressure spirals, worker thread exhaustion, TempDB contention, or blocking cascades by guiding a structured diagnostic workflow using Netdata health signals.

Core Features & Use Cases

  • Operator playbook triage flow via MCP: Routes an AI coding agent through a diagnostic tree using MCP queries against the same signals the Netdata operator playbook relies on.
  • Focused failure archetype diagnosis: Targets the dominant SQL Server failure modes (log/disk full, memory pressure spiral, worker exhaustion, TempDB contention, blocking cascade, and parameter sniffing).
  • Verification with load-bearing contexts: Re-runs MCP queries and validates that key mssql.* chart contexts return to expected ranges after remediation.
  • Use Case: An on-call engineer is paged due to elevated errors and latency on a SQL Server instance; this skill guides signal collection, anomaly ranking, root-cause narrowing, and remediation verification.

Quick Start

Ask the AI to troubleshoot Microsoft SQL Server using Netdata MCP by running the verification queries for the relevant mssql.* contexts and then recommending remediation based on the matching failure pattern.

Frequently Asked Questions about troubleshoot-microsoft-sql-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a Microsoft SQL Server memory pressure spiral or TempDB contention?

To troubleshoot SQL Server memory pressure or TempDB contention, query Netdata health signals via MCP to route diagnostics through an operator playbook, isolating root causes and validating remediation outcomes.

What is the best way to diagnose SQL Server log full or disk full incidents during on-call triage?

Diagnosing SQL Server log full or disk full incidents requires applying a structured Netdata diagnostic workflow to narrow root causes and validate that key mssql.* chart contexts return to expected ranges.

Can I use Netdata MCP queries to verify SQL Server remediation for blocking cascades?

Yes, Netdata MCP queries verify SQL Server remediation by re-running load-bearing mssql.* contexts over defined time windows, confirming blocking cascades have resolved and metrics returned to expected ranges.

Do I need Netdata instrumenting my SQL Server instance to diagnose worker thread exhaustion?

Yes, Netdata must instrument the SQL Server instance because this Skill relies on MCP-based Netdata health queries to collect the required mssql.* signals for diagnosing worker thread exhaustion.

How does the diagnostic tree identify failure archetypes like parameter sniffing in SQL Server?

The diagnostic tree identifies SQL Server failure archetypes like parameter sniffing by applying Netdata operator playbook logic to rank anomalies and narrow root causes based on collected health signals.