Many forms of disasters can happen to a database. Here are three I’ve seen lately.
4 Responses to “Forms of Database Torture (Illustrated)”
Leave a Reply
Read My Technical Blog Posts
I write and post videos about SQL Server, performance tuning, and more over on http://BrentOzar.com.
Read blog posts and watch videos I've created over here.
Read blog posts and watch videos I've created over here.
Speaking and Tweeting
Comments
- Wayne on Automating SQL Local Security Policy Rights: PoSH and NTRights
- Kendra Little on Be Prepared: Collecting Data from sp_WhoIsActive in a Table
- SGT_SQueequal on Be Prepared: Collecting Data from sp_WhoIsActive in a Table
- To the #SQLPASS #FirstTimers of #Summit 2012 – The Procrastination Edition | Scott Stauffer dot C-eh? on Seattle101
- Kendra Little on My Biggest Regret as a Database Administrator
- Andy Galbraith (@DBA_ANDY) on My Biggest Regret as a Database Administrator
- PASS 2012 Countdown – 1 Week To Go | Strate SQL on Seattle101



Here I thought when the database was on fire it was a good thing.
“We just moved all of our databases to Solid State Disks and now the Databases are on fire.”
“Yeah, they are smoking.”
That’s a good point. Smoking hot is good.
You just want to avoid making the ceiling sprinklers go off.
Excellent! here’s one: My Database is Bottlenecked
http://www.sqlsoldier.com/wp/wp-content/uploads/2012/03/DBBottleneck.jpg
Where are “fragmented” and “denormalized” ?