UPDATED BY
Brennan Whitfield | Aug 31, 2022

“Hug a Dba,” by Killa DBA, is by far the best hip-hop track I’ve ever heard about database administration. Granted, until I listened to his new full-length debut album with which it shares a title, it was the only song I’d ever heard about database administration.

What Is a Database Administrator?

A database administrator (DBA) is responsible for configuring, maintaining and securing an organization’s databases. Responsibilities typically include provisioning and patching databases and tuning queries. Other duties can include migrations, data modeling and data ingestion.

When we spoke, Killa DBA (given name Homer McEwen) nodded often as I asked him about the transitional moment in which database administration seems to be — upended by a series of technological and organizational shifts. The first verse of “Hug a Dba” directly references the DBA role’s diminished stature:

“Database management / Yes, that is the key / I remember back in the day when they treated us like kings / But today it’s not the same / Oh wait, is it just me? / The respect level isn’t quite where it should or used to be.”

What’s to blame for the database administrator’s decline in prominence? 

To answer the question, you have to look at the traditional core duties of a database administrator. Those include things like provisioning new databases, patching databases, tuning queries and maintaining back-ups — all of which are becoming mastered by machines and other new technologies.

Find out who's hiring.
See all Data + Analytics jobs at top tech companies & startups
View 2789 Jobs

 

Hug A DBA #KillaDBA | Video: Killa DBA

 

What Is the Future of the Database Administrator Role?

Cloud Computing

Today, a lot of DBA tasks are now partially or fully automated, thanks to the rise of cloud-managed databases. The big three cloud computing services each offer fully managed options, most notably Amazon RDS, Google’s Cloud SQL (which has service for MySQL, PostgreSQL and SQL Server) and Azure SQL Database.

Those who opt against migrating to managed databases sacrifice convenience for a level of control they probably don’t actually need, Asya Kamsky, principal engineer at MongoDB, previously told Built In

“You can still get access to all the logs,” and if you do need to provision a new machine, it’s a button-click away, she said. “I think that, in a few years, it’s just going to be inconceivable that we even considered hosting data centers ourselves.”

 

Automation

It’s not just nimble-minded startup culture that’s been affected. Automation has arrived in the legacy database world too. In 2019, Oracle released its autonomous database, which claims to automatically handle a slew of traditional DBA tasks. As TechRepublic noted, Oracle even advised database administrators at the time of its release to pivot toward the data architect role and embrace data modeling over “routine maintenance.”

 

DevOps

The other major sea change to rock traditional database administration in recent years is less technological, more structural: the rise of DevOps and site reliability engineering.

It’s uncommon to find the title “database administrator” in a startup. The closest analog is the site reliability engineer. The precise nature of SRE work varies by company, but it almost always involves writing code to automate routine processes, building tools to allow developers to work with infrastructure and taking on-call rounds to respond to any potential fires.

SRE emerged at Google in the wake of DevOps before catching on across the tech landscape. In short, DevOps was the turning-point union of development and operations. Traditionally separate, the two work together under the DevOps philosophy, with the operations side — which would include DBAs under the older paradigm — releasing, deploying and monitoring what the development team builds.

In a deflating irony, McEwen himself hadn’t disentangled administration from development in his own mind as he was starting his career in 1997. The split came from the top down at his then-employer, which favored a traditional corporate tech structure. 

“I thought they were all in the same — and they were all in the same, until [I was] at Home Depot,” he said. “They really split it up. We had developers, modelers, the admin, maybe even one or two more levels.”

Related Reading13 Tips for Quick, Accurate Data Wrangling

 

A Day in the Life of a Database Administrator

Of all the turbulence to hit database administration, the most disruptive event for McEwen was one that uprooted roles across the spectrum: the pandemic. He worked for 10 years as a DBA for a business travel agency that was suddenly faced with no business travel to manage. His last day was October 31, 2020.

Soon after, his time was devoted to a mix of freelance work, job prospecting and professional development — plus, of course, music.

McEwen spent two months on a contract assignment, helping a client combine two data centers into one at a new location. He returned to school, going for his master’s in computer science at Georgia Tech. And he fielded a couple of job interviews along the way, including one with Amazon, one with a company that found McEwen through his music. 

But McEwen’s recent professional experience offers a good window into what life as a DBA looked like circa 2020. It was a combination of subject matter expertise, incident response and running point for key infrastructure tools and projects.

McEwen was BCD Travel’s point man for Denoda, a data virtualization tool that essentially gives users a central view from which to query different — and different kinds of — databases. BCD was among the first companies to have a Denodo cluster, with three nodes, according to McEwen.

Other duties included specialized maintenance — McEwen was the subject matter expert for the company’s customer-facing DMZ database — and on-call duty once every seven weeks or so.

As for projects, McEwen headed up an ambitious migration, which moved databases off dozens of old servers and, in the process, upgraded each to SQL Server 2016. They also configured files to future-proof against potential IP address changes. A single database move might take as little as a week or as long as a month, depending on levels of complexity.

Stereotypes paint old-school DBAs as surly oppositionists who live to revoke access. But moves like the one described above — and McEwen’s perspective on them — betray a deep sense of cooperation.

“What was fun, I got to really know a lot of the people,” he said. “You meet the business owners, the application developers, the super users of the application, because you have to work with everyone to coordinate the migration.”

Of course, in other ways, McEwen’s experience couldn’t be more different than a typical DBA — which brings us to how that upgrade to SQL Server 2016 had significance beyond just infrastructure. McEwen was taken with advances in the database, so much so that it inspired his first technology-related track, a love letter to the new database simply titled “Sql Server 2017.”

The track was also something of a personal study aid, to make sure he knew the ins and outs of the new version to his bosses’ satisfaction. “I thought, if I put this in a song, I’ll have a leg up on my teammates,” he said. “I know my lyrics, so I’ll know the features.”

Related ReadingWhy Some Experts Hate the Hottest Trend in Data Viz

 

New Skills for Database Administrators to Learn

McEwen is well-positioned for transitional times in database administration.

On one hand, yes, database administration as traditionally defined is waning. Interest in the role has dipped slowly but steadily over the last 15 years, according to Google Trends data. On the other hand, database administrator employment is projected to grow eight percent by 2030, according to the U.S. Department of Labor Statistics.

The best explanation might have to do with overlap.

Due to the uncertain stability of the DBA role, two ways DBAs can still prove their worth in a post-managed database world is through owning ETL and streaming data tools, and also developing and implementing schemas, according to O’Reilly’s Introduction to Cloud Databases.

 

ETL and Data Streaming Tools

Those may now be considered the realm of data engineers and data architects, respectively, but DBAs often find their hands in related data work. McEwen, for instance, recalled the time that a team at his previous employer needed to upgrade from Access databases to SQL Server due to size and security limitations and ended up helping them model data and set up ETL processes.

“It wasn’t in the realm of our job description duties of what the admin is supposed to do. But because I was working with them so closely,” he said.

It’s the kind of thing that might repeat itself several times for a DBA across large organizations. “I probably had five or six processes that were not considered in our realm, but I wrote up detailed tutorials and had meetings with the BI team so that they could [smoothly] take it,” he said.

 

Cloud Database Technologies

McEwen is excited to dive further into cloud databases. When he left BCD, the company was about to take the full AWS plunge — Redshift, AWS Glue, Aurora, RDS, the whole nine yards. It was exciting for McEwen, who’d spent the majority of his time working with virtual machines and on-premises physical machines.

Still, he found opportunities to learn his way around the cloud beforehand. Like the time the company VP created his own Azure database, which turned business critical and had to be roped in by admin for security and maintenance.

 

Flexibility and Risk-Taking

You might even view the Killa DBA project itself as a kind of beyond-comfort-zones upskilling — one with greater risk than garden-variety professional development. Killa DBA proved to be a hit, and McEwen is now a beloved figure in the SQL Server community. But that was by no means guaranteed.

McEwen often finds himself the only Black person in a meeting room, or at a tech conference. In a panel discussion about diversity in data, he recalled the time two colleagues were urged by family to not relocate to Atlanta, because they claimed Black people there had been made violent by oppression.

Did such prejudice give him pause before taking his music public? He recalled Microsoft double-checking with him before posting about Killa DBA on the company blog in 2017. “They said: ‘Once we put this up, people are going to know who you are. Are you OK with that? They may say anything.’”

The tracks were just too good, he decided. And his willingness to perform paid off. To invoke “Hug a Dba,” the respect level was where it should be.

Great Companies Need Great People. That's Where We Come In.

Recruit With Us