Over a million developers have joined DZone.

The Constant and Constantly Changing Role of the DBA

DZone 's Guide to

The Constant and Constantly Changing Role of the DBA

Learn more about DBAs and where they're headed..or not headed.

· Database Zone ·
Free Resource

I've been working in and around data for over 30 years now. My title has changed a number of times and is poised to change again. My responsibilities have also shifted fairly continuously over that time. Even though it has been more than 20 years since I first took on the title of DBA, some aspects of the job are the same. However, over that 20 years, a stack of new technologies and processes have fundamentally changed a whole swath of what I do.

The DBA Song Remains the Same

Are your servers online? Are all databases available? Did the data load process run successfully last night? When was the last time a backup was run on this database?

I honestly don't care if you're in the cloud, on-premises, or in a hybrid situation. You are absolutely going to want to know the answers to these questions. In over 20 years on the job, these questions have been constant and the need to have an answer to them is the same as it ever was.

Yet, even within this constant set of questions, the needs and requirements, and frankly, how we go about getting the answers, has been changing. These constants and changes are reflected in the brand new "State of SQL Server Monitoring" report that Redgate has put together.

Oh, the DBA Times, They Are A'Changin'

If you think technology is going to let you stand still, you're kidding yourself. While there are many constants (when was the last time you tested a restore?), everything is moving faster and faster. We have to support, more, bigger, and faster-moving development teams. For these reasons and many others, I've been a fairly loud and consistent advocate for adopting DevOps methodologies.

I've seen the adoption of DevOps change organizations for the better. DevOps is a way to deliver better software, faster, to your production environments while simultaneously increasing the depth of protection on those same production environments.


I am a fierce believer in the fact that the role of the DBA is not going away. There will be DBAs for the foreseeable future. They're going to be tuning queries. They're going to be setting up sophisticated HA/DR configurations (even using the ones built into Azure, for example, work, maintenance, monitoring, is a fundamental aspect of what is necessary). They're going to be working. However, the work they do is going to be shifting. As such, they need a way to deal with the speed and magnitude of that change. The method that works best is DevOps.

So, even as my role changes a little (more on that soon), my advocacy for the DBA, whether they're doing traditional monitoring or implementing a fully automated Continuous Delivery deployment mechanism, is unwavering.

database ,dba ,role of dba ,database administrator ,devops

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}