explaingit

brentozarultd/sql-server-first-responder-kit

★ 3,798TSQLAudience · ops devopsComplexity · 2/5LicenseSetup · easy

TLDR

A set of SQL Server diagnostic stored procedures (sp_Blitz, sp_BlitzCache, sp_BlitzIndex, sp_BlitzFirst) that tell you exactly what's wrong with your database or why it's running slowly, with prioritized findings and fix documentation.

Mindmap

mindmap
  root((First Responder Kit))
    Main Tools
      sp_Blitz health check
      sp_BlitzCache queries
      sp_BlitzIndex indexes
      sp_BlitzFirst live check
    What it does
      Diagnoses slow SQL Server
      Prioritized findings
      Links to fix docs
    Tech Stack
      T-SQL
      SQL Server
      Stored procedures
    Platforms
      Windows SQL Server
      Linux SQL Server
      Amazon RDS
    Audience
      DBAs
      Backend developers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Run sp_Blitz on a SQL Server to get a prioritized list of health problems and configuration issues in minutes.

USE CASE 2

Use sp_BlitzCache to find which queries have been burning the most CPU or causing the most reads over time.

USE CASE 3

Run sp_BlitzFirst when a server is currently slow to get an instant snapshot of what is happening right now.

USE CASE 4

Audit indexes with sp_BlitzIndex to find missing indexes that would speed up slow queries or duplicate indexes wasting space.

Tech stack

T-SQLSQL ServerSSMS

Getting it running

Difficulty · easy Time to first run · 5min

Download the ZIP from releases and run a single SQL file against your server, no external dependencies.

MIT, use freely for any purpose, including commercially, as long as you keep the copyright notice.

In plain English

This is a collection of diagnostic scripts for Microsoft SQL Server, aimed at database administrators and developers who need to quickly assess what is wrong with a server or why it is running slowly. The scripts install as stored procedures, meaning they become callable routines that live inside your SQL Server database and can be run on demand. The main tools are sp_Blitz for an overall health check, sp_BlitzCache for identifying which queries have been consuming the most resources, sp_BlitzIndex for spotting missing or problematic indexes, and sp_BlitzFirst for diagnosing why a server is slow at this very moment. Additional scripts cover deadlock analysis, backup status, session management, and restoring databases. Each script produces output with context, such as priority levels that indicate urgency (lower numbers mean more serious problems) and links to documentation explaining what each finding means and why it matters. The output is designed to be read in SQL Server Management Studio or similar database tools. To install, you download a ZIP file from the releases page and run a SQL file against your server. The kit supports SQL Server running on Windows, Linux, and Amazon RDS. Azure SQL Database has partial support. Older unsupported versions of SQL Server may find working scripts in a Deprecated folder inside the repository. The project is maintained by Brent Ozar Unlimited and is licensed under MIT. Community support is available via a dedicated Slack channel, and bug reports follow a contributing guide in the repository. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
I just installed the SQL Server First Responder Kit. Walk me through running sp_Blitz and interpreting the Priority column in the output.
Prompt 2
My SQL Server is running slowly right now. What sp_BlitzFirst command should I run, and how do I read the output to find the bottleneck?
Prompt 3
I want to find the top 10 most expensive queries on my SQL Server. What sp_BlitzCache parameters should I use and what columns matter most?
Prompt 4
How do I install the SQL Server First Responder Kit on a SQL Server running on Amazon RDS, is the process different from a Windows install?
Open on GitHub → Explain another repo

← brentozarultd on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.