Data Monitoring / SQL Server Availability & Capacity
SQL Server: Database corruption response
Integrity checks return an error while reports still load. Preserve check output, affected object scope and backup availability.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
Integrity checks return an error while reports still load. Confirm the cause before choosing a fix.
Evidence to collect
Preserve check output, affected object scope and backup availability. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Escalate to the recovery procedure and verified backups before attempting repair options that can lose data. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for database corruption response 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.