SQL Server Performance Tune

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

The SQL Server Performance Tune page provides a guided performance review for server-level or database-level SQL Server tuning. It is designed for practical investigation of expensive workload and configuration risks.

When To Use Performance Tune

Users report slow applications.
CPU, memory, waits, or I/O pages show pressure.
Query Store or cached SQL identifies expensive statements.
You want a structured tuning pass before deeper manual analysis.

Workflow

Open Performance Tune for the server or database.
Review the findings and recommendations.
Open related query, wait, health, and index pages for supporting evidence.
Open Performance Tuning With AI when you want Mini DBA AI Assistant to explain the evidence or suggest a safe tuning order.
Apply changes in a controlled maintenance process.
Re-check the same page after the change to confirm improvement.

What Performance Tuning Should Include

Good SQL Server performance tuning uses more than one signal. A slow query may need an index, but it may also need a query rewrite, statistics update, plan review, memory grant review, or application change. A high-wait server may need storage work, but it may also need query tuning to reduce I/O.

Use Performance Tune as a structured starting point, then validate recommendations with:

Cached SQL for current expensive statements.
Query Store for history and plan changes.
SQL Server Execution Plans for operator drill-down, warnings, missing index evidence, and AI plan review.
Waits for bottleneck categories.
Indexes for index opportunities.
Health Checks for configuration and operational risks.

SQL Server Performance Tuning FAQ

Should I add every suggested index?

No. Indexes speed up some reads but add write cost and maintenance overhead. Test changes and consider workload balance.

How do I prove a tuning change worked?

Compare before and after metrics: duration, CPU, reads, writes, wait profile, and Query Store history. Also confirm user-facing performance improved.

Is performance tuning only query tuning?

No. Query tuning is central, but memory, CPU, I/O, configuration, maintenance, and blocking can all affect SQL Server performance.