Data Monitoring / SQL Server Query Performance
SQL Server: Query Store capture coverage
A problematic query is absent from the expected historical view. Inspect Query Store state, capture policy and the time period of interest.
Environment and inputs: SQL Server 2019–2025 where the referenced feature is supported; Query Store and diagnostic collection require appropriate configuration and permissions. Azure SQL behavior can differ.
Failure scenario
A problematic query is absent from the expected historical view. Confirm the cause before choosing a fix.
Evidence to collect
Inspect Query Store state, capture policy and the time period of interest. Record the time, affected scope and a healthy comparison interval.
Worked diagnostic example
Read-only SQL Server Query Store state inspection in the current database.
SELECT actual_state_desc, desired_state_desc,
readonly_reason, current_storage_size_mb, max_storage_size_mb
FROM sys.database_query_store_options;Fix the confirmed cause
Correct collection coverage through the approved process before concluding that the query never ran. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for query store capture coverage using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.