The SQL Server Indexes page helps review database index health and index-related tuning opportunities.
What To Review
- Indexes for a selected database.
- Usage patterns.
- Size and maintenance signals.
- Missing, unused, duplicate, or inefficient index opportunities where available.
- Relationship between indexes and expensive queries.
Workflow
- Open a SQL Server database.
- Select Indexes.
- Review high-impact findings first.
- Compare with Cached SQL, Query Store, and Performance Tune.
- Test index changes safely before applying them to production.
How To Review SQL Server Indexes
SQL Server index tuning should start with workload evidence. Use Cached SQL, SQL Server Query Store, and SQL Server Activity to identify the statements causing the most cost, then use this page to review the indexes that support those statements.
Missing, unused, duplicate, and inefficient index findings are starting points, not automatic change scripts. A missing index may improve one query but slow writes or increase storage. An apparently unused index may support a monthly process, a rare support workflow, or a constraint. Review execution frequency, write overhead, table size, and business purpose before adding or removing indexes.
After a change, compare query duration, reads, writes, waits, and plan behavior over a similar workload period. This helps prove whether the index change solved the problem or moved pressure somewhere else.
SQL Server Index FAQ
Should I create every missing index suggestion?
No. Validate each suggestion with query evidence, write overhead, storage impact, and testing.
Why can unused indexes still matter?
Some indexes support rare but important queries or constraints. Confirm business usage before dropping them.
Which page should I use before changing indexes?
Use Query Store, Cached SQL, Activity, and Performance Tune to understand workload impact first.