SQL Server Query Store

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

The SQL Server Query Store page uses SQL Server Query Store data to analyze query performance history, plan changes, and resource usage over time.

Requirements

Query Store requires SQL Server 2016 or later and must be supported and enabled for the database being analyzed. Mini DBA may show an unsupported message for editions or versions that do not support Query Store.

What You Can Review

Top resource-consuming queries.
Time-windowed query performance.
Query plan buckets.
Query Store status and properties.
Execution plans where available, including operator drill-down and AI plan review.

Workflow

Open Query Store for the SQL Server.
Choose the time range.
Review top resource queries.
Select a query to inspect plan buckets.
Load a plan for detail when available and review SQL Server Execution Plans.
Compare with Cached SQL for current cache behavior.

Why Query Store Matters

SQL Server Query Store keeps query performance history inside the database. That makes it valuable for regressions, plan changes, and before/after comparisons. Cached SQL tells you what is expensive now; Query Store helps show whether the query was always expensive, recently regressed, changed plans, or became expensive after a release.

When a Query Store query has multiple plans, use the plan buckets to identify the plan tied to the bad time range, then open the execution plan and compare expensive operators, warnings, missing index evidence, and parameter clues.

Use Query Store when investigating:

A query that became slower after a deployment.
A plan regression.
Parameter-sensitive behavior.
Resource consumption over a selected time window.
Whether a fix improved duration, CPU, reads, or writes.