AH-HA! You didn’t know there would be one of these, did you, hotshot? You’ve been reading along in the series, just smiling and nodding, pretending you’re keeping up, but not really doing the homework. BUSTED! Put your books away and get your pencils out.
Backup & Recovery Questions:
- How many production SQL Servers do you have?
- What’s the RPO and RTO of your most important production server?
- Did your backups take the normal amount of time last night?
- When was the last time DBCC CHECKDB successfully finished in production?
- How many different people are sysadmins in production?
- Do they each know that they’re sysadmins, and take care to avoid accidents?
- How many of your databases hold personally identifiable data like credit card numbers, social security numbers, and passwords?
- If someone gets hold of one of those database backups, can your company’s data go public?
- Have you informed your managers of that risk, or will they blame you?
- When a database server runs out of drive space, who gets emailed?
- Do at least two different people get the email in case one is on vacation or unavailable?
- What actions will you take to fix the situation?
- Are those actions documented so that everyone who gets the email can take action quickly?
- Does every table in production have a clustered index?
- For any exceptions (heaps), do you have a plan to fix them?
- Which table in production has the most indexes, and why?
- Which frequently queried tables in production have the least indexes, and why?
- How are you managing index fragmentation?
The Right Answers
There’s no one right answer for any of these questions, but some answers are more wrong than others. Database administration is a journey, and not everyone in the company is going to appreciate the work you’re putting in. You can spend weeks or months trying to improve your answers on these. No matter how big your company is and how many database administrators you have, you’re probably never going to be truly happy with your answers here.
You’re not aiming for perfect.
You’re aiming for good enough that your managers accept the base of your Database Hierarchy of Needs pyramid, and that you feel confident in tackling the higher levels like performance and future-proofing.
Next week’s email is going to start digging into performance, and we’re going to ignore the lower levels of the pyramid – but that doesn’t mean that part of your journey is over. Print out this email, cut out the question list, and scribble in a few thoughts. Pin it up on your wall, and a few months from now, when you’re feeling overconfident that your environment is awesome, check that list again. Refresh your memory with the links on the right side of this email.
When an outsider comes in, like a support engineer or a consultant, they’re going to start at the base of your pyramid first. Before they start to help, they have to make sure your data is backed up and checked for corruption. They can’t go making changes without having a safety net.
And you shouldn’t either.
Now might be a good time revisit some of the posts in the DBA Training Plan series.