Live registration reopens October 1, 2026, in 17d 19h 37mNotify me

Production DBA

My Favorite Database Disaster Stories

The statute of limitations has passed, so this week on SQL Server Radio, I get together with Guy Glantser and Matan Yungman to talk about our favorite oops moments.

I talked about my very first database disaster ever – done back when I was in my 20s and working for a photo studio, using Xenix, long before I ever thought I wanted to be a database administrator. (Yes, kids, Microsoft had their own Unix thirty years ago, and suddenly I feel really, really old. No, I wasn’t using it thirty years ago.)

This episode was so much fun because we recorded it in-person, together, gathered around a table in Tel Aviv when I was there for SQLSaturday Israel 2016. I really love talking to these guys, and I think you can hear how fun the chemistry is on the podcast.

Head on over and listen to our disaster stories, and when you’re done, check out my classic post 9 Ways to Lose Your Data.

Free, 3× a week

Get my new posts by email

Three posts a week, plus a Monday roundup of the best database news from around the web.

6 comments

  1. Those disaster stories sure make SQL Azure seem more attractive. Seems like most organizations will want to leave backup and recovery to a cloud provider going forward, rather than trying to do it themselves.

      1. Yes, of course there was always that possibility, but organizations have to compare the reliability of a backup and recovery system they set up for themselves versus what they can get from a cloud service provider.

  2. Hi Brent, I have a question about HA&DR, what is the correct desition, implement SQL Server HA&DR models or implement third party solutions like MIMIX Share from Vision Solutions?
    Nobody speak about this topics in HA&DR.

    1. Stiven – it all depends on your app and your SQL Server’s RPO/RTO. For third party solutions, I’d ask to talk to some of their satisfied clients.

Leave a comment

Your email address will not be published. Required fields are marked *

Email me about new comments: