Role guide · Databases
What is a DBA?
What a database administrator does day to day and how people reach the role, depending on which kind of DBA the job ad is asking for.
DBA stands for Database Administrator: the person who makes sure a company's databases stay available and perform well, and that data is neither lost nor touched by the wrong people. It is an infrastructure role, not an analytics one: a DBA does not exploit the data, they make it safe for others to do so.
What a DBA does day to day
- Availability. Keeping the database up and answering. High availability, replicas, failover, maintenance windows.
- Performance. Indexes, execution plans, slow queries, locks. A good part of the job is finding out why something is slow and fixing it without touching the application.
- Backup and recovery. Backup policy and restore drills, including point-in-time recovery. This is what separates an incident from a disaster.
- Security and access. Users, roles, encryption, auditing, compliance.
- Changes and deployments. Schema migrations, version upgrades, cloud moves, capacity.
- Support to development. Reviewing models, advising on indexes, looking at the queries that run slow and helping when something breaks.
Types of DBA
The label covers fairly different profiles, and it is worth knowing which one describes you before you apply:
- Production or operations DBA. The classic one: many servers in critical environments, with on-call. Usually comes from systems administration.
- Development DBA. Closer to the code: modelling, stored procedures, execution plans and slow queries. Usually comes from backend development.
- DBRE or cloud DBA. Managed databases (Azure SQL, RDS, Cloud SQL) and infrastructure as code. More and more common in job ads.
How people become a DBA
Almost nobody starts as a DBA. The two usual paths are from systems administration (you already run servers and backups, and you specialise in the engine) and from backend development (you already write SQL, and you move towards performance and operations). In both cases what makes the difference in an interview is being able to talk through a real incident: what broke and what you changed so it would not happen again.