SQL Horror Stories
summary
A run of cautionary tales shows concrete failures and fixes: a manager blocks preventative scripts to speed deployments and the team pays with repeated midnight pages until reputational leverage forces the change; backups reveal backups that won't restore because corruption only shows on recovery; an organisation loses TDE protection by keeping the certificate on C: and getting hit by Petya; multiple stories hinge on missed DBCC checks, sloppy password habits, and recovery taking days.
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
54m10 Deadly Sins of SQL Server Configuration
05mCommon mistakes of DBAs
34mWar Stories: Fighting the PostreSQL Support Trenches
47mDisaster Recovery Strategies for SQL Server
20mDave & James’ Excellent Database Adventure: From Code Errors to Reliable Releases
39mData Corruption: Stop the Evil Tribbles
