How relevant is the DBA in the cloud era?

Performance optimization

Sure, Azure SQL Database offers certain automatic optimizations (create and drop index, force last good plan), but specific configuration and query tuning work is often still needed to get the best performance for your particular application (think long-running queries, parallelism issues, and so on). A DBA can help identify and address performance problems.

Security and compliance

Although Azure SQL Database comes with built-in security features, such as advanced security and Azure Active Directory integration, access management, audit logging, and compliance with industry regulations still need attention. Applying the principle of least privilege in your database remains a careful, ongoing task. A DBA can manage these aspects for you.

Data migration

If you’re migrating data to Azure SQL Database, a DBA can help plan and execute the migration, making sure data integrity is preserved throughout. There are many ways to migrate data: bcp, SSIS, DMA, SSMA, Azure DMS, SQL Data Sync, and BACPAC. And that list still isn’t complete. Each of these approaches comes with its own trade-offs in downtime, simplicity, and cost.

Continuity and recovery

DBAs can develop and maintain backup and recovery strategies to make sure your data is protected and that you can recover quickly in the event of a failure, taking your desired recovery time objective and recovery point objective into account.

Automation and scalability

A DBA can build automation scripts to simplify tasks — think scaling the database based on workload, or rolling out new features.

Monitoring and troubleshooting

Monitoring performance and tracking down problems remains a DBA task, even in a DBaaS environment. A DBA can use tooling to keep an eye on database health and resolve issues when they arise.

Keeping an inventory

It’s also worth maintaining an inventory or CMDB of your databases. If you don’t know which databases exist, how can you manage them? That might not matter much for organizations with just a handful of servers, but once the number grows, it’s easy to lose track of a SQL Server or a cloud database entirely.

That’s already an easily forgotten task on-premises, but in the cloud it gets even trickier, given how easy it is to spin up a new database. Ideally, you’d already build inventory updates into your IaC (Infrastructure-as-Code) pipeline.

Cost management

DBAs can help manage the cost of Azure SQL Database, for example by making sure you’re using the right service and scaling tiers, and by identifying and eliminating unused resources.

Conclusion: from DBaaS to DeDBAas, DBA expertise remains crucial, even in cloud management

Although Azure SQL Database automates a lot of tasks and simplifies management, a DBA’s expertise remains valuable in making sure the database performs optimally, stays secure, and meets your organization’s unique needs. The specific scope of a DBA’s work in an Azure SQL Database environment can vary, depending on the complexity of the deployment and the organization’s requirements.

Food for thought: hire a DBA full-time, or bring one in part-time?

One question worth genuinely considering is whether you still want to employ a full-time DBA in-house. Because a lot of the regular (read: old-school) management tasks fall away once the “as-a-Service” model automates them, that DBA may end up spending less time on the work they used to do.

At some organizations, that DBA’s role partly shifts toward Data Steward or Data Engineer. Over the longer term, there’s a risk you end up with no direct, in-depth database expertise in-house anymore. In other cases, the DBA role shifts toward DevOps, with the DBA operating more as a Database Reliability Engineer.

A large DBA team with deep database expertise

OptimaData has a large team of experienced Database Platform Engineers and multi-platform Database Reliability Engineers operating at Champions League level. Just like you pay for a cloud database based on hourly usage, OptimaData’s expertise can be brought in on demand too. The big advantage: the certainty of having deep, hands-on expertise within reach, for a fraction of the cost of traditional in-house management. And someone who steps in when it’s needed, even in the middle of the night if that’s what it takes.

Migration advice from a database expert

Before you even get that far, there’s still the question of which Azure SQL option you’ll use (SQL Server on Azure VMs, Azure SQL Managed Instance, or Azure SQL Database), or even a mix of the three. And if you go with Azure SQL Database, which purchasing model do you choose: DTU or vCore (and within that, provisioned or serverless)? How do you integrate the tooling Azure offers, and how do you shape the migration itself? The options are plentiful, and input from an independent database expert makes a real difference.

Want to know more?

Thinking about migrating to the cloud, or considering reorganizing your management team? OptimaData can help you make the right choices, guide you through a migration-readiness program, or map out your cloud and management costs through a benchmark. Want a Trusted Advisor on hand for the “just in case” and “who you gonna call” moments? Feel free to ask about the possibilities.