Data Monitoring / SQL Server Query Performance
SQL Server: Extended Events scope
A broad diagnostic session creates excessive monitoring overhead. Review captured events, predicates, targets and retention for the actual incident question.
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 broad diagnostic session creates excessive monitoring overhead. Confirm the cause before choosing a fix.
Evidence to collect
Review captured events, predicates, targets and retention for the actual incident question. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Use a bounded targeted session and measure collection overhead before leaving it enabled. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for extended events scope 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.