A DBA's Guide to the Proper Handling of Corruption
summary
Explains how to detect and respond to physical file corruption using only built‑in SQL Server tools: SQL Agent alerts, the suspect_pages table, DBCC CHECKDB (use ALL_ERRORMSGS and NO_INFOMSGS), and scripted alerts for severity ≥19 plus error 825. Emphasizes tested restores over snapshots or relying on AGs, warns that running REPAIR_ALLOW_DATA_LOSS without Microsoft guidance can silently drop data, shows index disable/rebuild and when a restore is the only safe option.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:27What is database corruption
- 7:12Monitoring corruption with SQL tools
- 13:13Using CHECKDB effectively
- 16:34Repair ALLOW_DATA_LOSS risks
- 20:05Backup and restore strategies
- 24:03Virtualization and backup misconceptions
- 26:37Clusters and availability groups
- 28:03Incident management process
- 30:55First steps during corruption
- 33:06Assessing corruption impact
- 34:29Demo: Index corruption recovery
- 37:42Demo: TempDB corruption recovery
- 38:23Demo: Unknown corruption case
- 45:55Demo: System page corruption
- 51:11Summary and Q&A
related talks
51mDatabase in Distress: Testing and Repairing Different Types of Database Corruption
21mSQL Horror Stories
52mData Corruption Bugs: Diagnosis and Lessons
20mDebugging Data Corruption in PostgreSQL
37mDatabase in Distress: Testing and Repairing Different Types of Database Corruption
32mDebugging Data Corruption in PostgreSQL: A Systematic Approach
39mData Corruption: Stop the Evil Tribbles
01mAre you an "accidental" DBA?
