SQL Horror Stories
summary
A rapid set of real incidents: a preventative‑maintenance script rollout is blocked until a manager is reframed by reputation and then deployed, saving hours of firefights; backups prove unusable so recovery requires rolling back to a 10 days old copy and exporting corrupted tables; corruption checks via DBCC CHECKDB are non‑optional; ransomware destroys keys because a TDE certificate on C drive breaks recovery. Tools named: Ola scripts, DPA, SolarWinds observability.
AI-written summary · about
chapters (8)
- 0:00SQL horror stories intro
- 3:04Bad bosses and ego
- 8:24Troublesome teamwork
- 11:44Vendor session
- 13:12Security failures
- 15:43Database recovery
- 18:17Corruption and neglect
- 19:24Final queries
related talks
21mSQL Horror Stories
21mSQL Horror Stories
38mProtecting Database Backups From Ransomware and Malicious Intent
51mDatabase Incident Management: When Everything Goes Wrong
54m10 Deadly Sins of SQL Server Configuration
47mDisaster Recovery Strategies for SQL Server
51mDatabase Disasters and How to Find Them
20mDave & James’ Excellent Database Adventure: From Code Errors to Reliable Releases
