sqlserver-health-check

Diagnose SQL Server instance health by analyzing DMVs, wait statistics, and blocking chains.

Updated Feb 19, 2026

Search Tags:#troubleshooting #health check #performance tuning #sql server #database administration #blocking #wait statistics

Ready to run

npx skills add https://github.com/rudi-bruchez/dba-skills --skill sqlserver-health-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlserver-health-check
Source: https://github.com/rudi-bruchez/dba-skills/tree/main/skills/sqlserver-health-check
Command: npx skills add https://github.com/rudi-bruchez/dba-skills --skill sqlserver-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and examples (resource) components.

What problem does it solve?

This Skill helps identify and diagnose performance bottlenecks, slow response times, and errors within a SQL Server instance, ensuring optimal database health and availability.

Core Features & Use Cases

Performance Diagnostics: Analyzes wait statistics, blocking, memory pressure, CPU usage, and I/O latency.
Health Audits: Provides a comprehensive overview of instance vitals and database states.
Troubleshooting: Pinpoints root causes for slow or unresponsive SQL Server instances.
Use Case: When users report that SQL Server is slow, run this skill to quickly identify if the issue is due to high I/O latency, CPU contention, or excessive blocking.

Quick Start

Run the sqlserver-health-check skill to analyze the current performance of the SQL Server instance.

Frequently Asked Questions about sqlserver-health-check

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

FAQPage Schema

How do I diagnose SQL Server performance issues using wait statistics and DMVs?▼

To diagnose SQL Server performance issues, this Skill queries dynamic management views to analyze wait statistics, blocking chains, memory pressure, CPU usage, and I/O stalls. It pinpoints root causes for slow or unresponsive instances by evaluating these system metrics.

What's the best way to check SQL Server health and identify blocking chains?▼

The best way to check SQL Server health is running a comprehensive audit that analyzes DMVs for blocking chains, I/O latency, and memory pressure. This identifies whether slow performance stems from high I/O latency, CPU contention, or excessive blocking.

Do I need special permissions to run a SQL Server health check?▼

Yes, you need direct SQL Server connectivity and appropriate permissions to query system dynamic management views. These permissions are required to access the DMVs that provide wait statistics, blocking chains, and memory pressure data for the health audit.

Can I use this SQL Server troubleshooting approach for routine database health audits?▼

Yes, you can use this SQL Server troubleshooting approach for routine health audits. It provides a comprehensive overview of instance vitals and database states by checking database integrity, CPU usage, and I/O stalls to ensure optimal database health and availability.

Why does SQL Server experience high I/O latency and how can I find the root cause?▼

SQL Server experiences high I/O latency due to bottlenecks in disk subsystems or excessive blocking. This Skill finds the root cause by analyzing I/O stalls, wait statistics, and memory pressure, determining if the issue stems from CPU contention or disk latency.