Data Monitoring / SQL Server Availability & Capacity
SQL Server: Tempdb capacity pressure
Temporary work consumes available tempdb space during a report batch. Separate user objects, internal objects and version-store contribution where supported.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
Temporary work consumes available tempdb space during a report batch. Confirm the cause before choosing a fix.
Evidence to collect
Separate user objects, internal objects and version-store contribution where supported. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Address the dominant producer and validate headroom under the next representative batch. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for tempdb capacity pressure 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.