It’s spooky season, so I thought I’d give my top five Slack or Teams messages that may cause database professionals nightmares. Though there are only five here, they range from messages that are “subtle” to “jump scare” level.
Feel free to comment below and add your own to the list.
“I talked to so-and-so, they said it’s a database issue.”
Of course they did. So-and-so may have done all the proper research to back up that claim. Still, sometimes it’s hard not to get defensive. Especially if that’s the first thing someone says when reporting a problem.
“We don’t have backups of that. Don’t YOU manage backups?”
A database administrator’s reach can only go so far. Make sure that reach is clearly documented in case someone comes unjustly pointing fingers.
“We have backups of the X database, right?”
We do, but why are you asking? That opening question sets off all kinds of alarm bells. This type of question is a little different from the last point, as it shouldn’t make you question your own belief in backups, it should make you fear what restore work lies ahead.
“Someone was looking into that database corruption issue we got an alert about, and someone else restarted the server…”
Grab an extra coffee because you might have a long night ahead.
“Can you just update it in the database? This change shouldn’t break anything.”
“Why would I wear a seat belt? I’m not going to crash. Forget sunscreen, I only plan on being outside a few minutes.”
Same energy. Remember, no one is invincible.
Perhaps you’re right about that update or script, and it probably won’t break anything. But what if it does? Sometimes, there are justifiable exceptions, but there’s a process for a reason. Don’t fall into the “we don’t always test, but when we do, it’s in prod” group.
Thanks for reading and have a happy Halloween!
Chad Callihan 