10 Unseen Things Successful DBAs Do

It was 19 F at 5:15 AM as I laced up my hiking shoes. That’s cold for my part of the world. Each morning, I walk two to four miles to get the day started. Why? I’m preparing for my next 150-mile trek along the Appalachian Trail. I put in the time now so I can be successful then. As I walked this cold January morning, unnoticed by people in their warm homes, it occurred to me that this is what successful DBAs do. They put in the unseen work so that when the time comes, they can be successful.

What do successful DBAs do when no one is watching?

Successful SQL Server DBAs work behind the scenes to ensure the SQL Server environment is as stable, secure, and performant as possible. Here’s a list of some of the things we do when no one is looking.

1. Verify backups. The backup job completed successfully, but that doesn’t necessarily mean you can restore from it. Periodically verify your key database backups.
2. Perform test restores. You don’t need a backup plan. You need a restore plan. By periodically restoring databases to test systems you can verify the backups are good, run CHECKDB against the restored database, have an estimate for how long it’ll take to restore to production if needed, and refine the documentation so someone else can do it if you’re on vacation.
3. Review error logs. SQL Server, SQL Agent, and Windows error logs can contain a wealth of important information. Check them daily.
4. Review alerts and notifications. Successful DBAs don’t like calls that start with “The database seems to be down, can you check on it?” You want to know before the call comes in. Read the alert emails that come in.
5. Check HADR. Those Availability Groups and Failover Cluster Instances are great, if they are working. Check them daily
6. Actively monitor. Proactive monitoring software can be great, but not if it becomes shelfware. Learn to use it, tune it, and check it.
7. Benchmark. Knowing what is a normal will help you troubleshoot any abnormalities that may rise. You can also use the information to predict when additional resources will be needed to support the anticipated growth. As a side benefit, benchmarking metrics can also arm you with proof that it’s not the database that’s slow.
8. Patch. The old adage “If it ain’t broke, don’t fix it” does not apply to DBAs. Patch your test systems, then production systems. Regularly.
9. Automate. Building a script library to help automate some of these tasks will save you a lot of time, effort, and mindless repetition.
10. Stay up to date. Things change fast. Successful DBAs continually learn and hone their skills. Don’t become complacent.

Of course, this isn’t a comprehensive list of all the responsibilities of a DBA. We do much more. From tuning queries to designing data environments, from discussing Recovering Time Objectives (RTOs) and Recovery Point Objectives (RPOs) with key stakeholders to working with application vendors and developers, DBAs are not an idle group.

Don’t have a DBA and not sure where to get started? Check out Working Without A SQL Server DBA? Do These 10 Things Now.

This is what we do

Many of our clients can’t justify a dedicated full-time DBA to keep their SQL Servers healthy. That’s where we help. We bring the tools, processes, and SQL Server expertise they need to keep their SQL Server infrastructure reliable, secure, and performant.

Some of our clients have a DBA team. We support them by taking some of these important tasks off their plates so they can focus on the things that require deep institutional knowledge. We also become the trusted source for support when they face a problem they haven’t seen before.

Want to learn more about how SEROShield helps companies? Let’s talk.