sqlplan-compare

Compare two SQL Server execution plans to identify performance changes.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanterx/mssql-performance-skills --skill sqlplan-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sqlplan-compare
Source: https://github.com/vanterx/mssql-performance-skills/tree/main/skills/sqlplan-compare
Command: npx skills add https://github.com/vanterx/mssql-performance-skills --skill sqlplan-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compares two SQL Server execution plans for the same query to identify exactly what changed and caused a performance regression.

Core Features & Use Cases

  • Side-by-side plan comparison highlighting differences in join strategies, memory grants, operator topology, spills, and missing indexes.
  • Surface actionable findings with a prioritized fix list for quick remediation.
  • Ideal when a deployment, statistics update, or schema change regresses query performance.

Quick Start

Provide two SQL Plan files (baseline.sqlplan and new.sqlplan) to generate a diagnostic delta report.

Frequently Asked Questions about sqlplan-compare

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

FAQPage Schema
How do I compare two SQL Server execution plans to find what caused a query performance regression?

To compare SQL Server execution plans, you provide a baseline and a new .sqlplan file. The diff identifies changes in joins, memory grants, and operator topology that caused the performance regression.

What changes in an execution plan should I look for after a statistics update or schema change?

When analyzing an execution plan after a statistics update or schema change, look for differences in join strategies, memory grants, operator topology, spills, and missing indexes to pinpoint the regression cause.

Can I use .sqlplan files from both production and test environments to diagnose query slowdowns?

Yes, you can provide .sqlplan files captured from either production or test environments. The analysis surfaces the execution plan delta to identify what changed and guides your remediation efforts.

What is the best way to generate a prioritized fix list from baseline and new SQL plans?

The best way to generate a prioritized fix list is to diff the baseline and new SQL plans. This produces a diagnostic delta report highlighting actionable findings for quick remediation of the query regression.

Why does my SQL query performance regress after a deployment, and how do I identify the exact cause?

Query performance regresses after a deployment when the execution plan changes. By comparing the baseline and new plans, you can identify exact changes in joins, spills, and missing indexes to find the specific regression cause.