SQL Horror Stories
summary
Guided tour of real failures: backups often succeed but restores fail, forcing recovery from 10+ day-old copies; DBCC CHECKDB is cited as mandatory before a restore; one team exports corrupted tables, rebuilds the DB and reloads rows — recovery takes days. A TDE certificate kept on C: is lost to Petya ransomware and encrypts everything. Mentions SolarWinds DPA and observability tools, a booklet giveaway of SQL in a Nutshell (25 printed copies), and many laughable, avoidable SQL coding mistakes.
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
47mDisaster Recovery Strategies for SQL Server
53mA DBA's Guide to the Proper Handling of Corruption
47mDisaster Recovery Strategies for SQL Server
05mCommon mistakes of DBAs
20mExcellent Database Adventure: From Code Errors to Reliable Releases
38mProtecting Database Backups From Ransomware and Malicious Intent
