A guided path
A diagnostic query starts the investigation.
Dynamic management views, cache, Query Store, and events preserve different kinds of evidence. Some views describe current state; others accumulate data since a restart or depend on a plan remaining available.
The path separates observation, hypothesis, and action. A high wait, an index suggestion, or an expensive query needs context before it becomes a recommendation.
How to use it
How to interpret each value.
- Distinguish the observed periodSeparate current state, accumulated data, cache, and intervals retained by Query Store.
- Relate several signalsAn isolated metric directs the investigation, but rarely proves a cause.
- Review permissions and costAdministrative queries may require elevated permissions or scan an entire instance.
- Define the next checkEach result leads to a more precise question and a delimited check.
Editorial method
Evidence-based conclusions.
Queries state permissions, time scope, and conditions that can alter the output. Accumulated results describe their observation period. A correlation requires checking the cause.
High-impact actions—terminating sessions, clearing plans, changing configuration, or creating indexes—remain outside a blind recommendation. The hypothesis and possible side effects are reviewed first.
Read the editorial methodologyThe path
Activity, resources, and changes.
The path begins with what is happening now and expands the investigation toward trends, structures, and regressions.
Active work, blocking, and transactions
Queries for observing requests, reconstructing blocking chains, and distinguishing sessions that retain open work.
Waits and accumulated consumption
Signals for reviewing waits, CPU, reads, and duration without confusing accumulation with cause.
Plans, indexes, and statistics
Cached plans, suggestions, usage, fragmentation, and statistics state as evidence that requires context.
Space, log, events, and regressions
File usage, log reuse, deadlocks, and performance changes observed through Query Store.
Resources and plan stability
tempdb, memory grants, per-file latency, and queries that retained multiple plans.