Skip to content
Knowledge Hub/Article
Article

What Is a DBA? What Does a Database Administrator Do?

A DBA installs, backs up, tunes and secures an organization's databases. What the job involves, the main types of DBA and how the role differs from DBaaS.

Oğuzhan Gerçek··7 min read
What Is a DBA? What Does a Database Administrator Do?

Short answer: A DBA (database administrator) is the specialist who installs, upgrades, backs up and monitors an organization's databases and controls who can access what. The job is to make sure data is not lost, only authorized people can reach it, and queries run fast. High availability, replication and capacity planning are part of the role too. With a managed database service (DBaaS), installation, patching and backups move to the provider, while query tuning and application optimization stay with the customer.

What is a DBA?

Oracle's Database Administrator's Guide states that each database requires at least one database administrator. As a system grows and gains users, database administration is sometimes not a one-person job but the work of a group of DBAs who share responsibility. The US Bureau of Labor Statistics (BLS) describes database administrators and architects as people who create or organize systems to store and secure data.

A database is a system where data is stored in structured form and can be queried. The DBA is responsible for keeping that system healthy from the day it is built until the day it is decommissioned. Which database engine to choose is a separate decision; we compare PostgreSQL and MongoDB in this article.

What does a DBA do?

Oracle's list of responsibilities and the BLS job description overlap in six areas:

  • Installation and upgrades: Installing the database software and applying patches and new versions in a planned way.
  • Backup and recovery: Designing the backup strategy, taking backups and restoring them when needed.
  • Performance: Finding slow queries, keeping indexes and statistics current, and allocating resources among user groups.
  • Security and access: Enrolling users, granting permissions and monitoring access to the database.
  • High availability and replication: Keeping a second server ready to take over quickly if the primary fails, and monitoring replication lag.
  • Capacity planning: Allocating storage and planning future requirements ahead of time.

The PostgreSQL documentation spells out the routine part of the job: setting up scripts for regular maintenance tasks and checking that they run successfully is the database administrator's responsibility. Chief among those tasks are regular backups, VACUUM, and updating the statistics the query planner relies on.

Why backup and recovery come first

In the words of the PostgreSQL documentation, without a recent backup you have no chance of recovery after a catastrophe such as a disk failure, a fire or a critical table dropped by mistake. PostgreSQL offers three fundamentally different approaches to backup: SQL dump, file system level backup and continuous archiving. Continuous archiving combines a file system backup with a backup of the write-ahead log (WAL) files, which record every change made to the data files, so the database can be restored to a consistent state as of any point in time (point-in-time recovery).

Whether a backup works only becomes clear when you restore it. How many minutes of data loss are acceptable (RPO) and how long recovery may take are questions to answer before choosing a method. We cover backup types and the 3-2-1 rule in our backup article, and why replication is not a backup in our replication article.

Upgrades: keeping track of support dates

Every database version has a support lifetime, and those dates belong on the DBA's calendar. The PostgreSQL project supports each major version for 5 years after its initial release, shipping bug fixes and, if needed, security fixes in minor releases at least once every three months. When the period ends, a final minor release comes out and the major version reaches end of life. For PostgreSQL 14, that date is November 12, 2026.

Commercial databases follow the same pattern. According to Microsoft's lifecycle page, extended support for SQL Server 2016 ended in July 2026; the page lists Extended Security Updates (ESU) periods after that date. Major upgrades are not simple updates either: PostgreSQL requires a dump and reload of the database or the pg_upgrade tool. They are best run as projects, with testing, application compatibility checks and a rollback plan.

Security: the DBA's own privileges are a risk

NIST defines least privilege as restricting users' access privileges to the minimum necessary to accomplish assigned tasks. In the database, the DBA is the person who enforces that principle, yet the DBA usually holds the broadest privileges as well. According to Oracle's documentation, SYSDBA is the most powerful administrative privilege, allowing most operations, including viewing user data.

That is why administrator accounts should be few, shared accounts should be avoided, and every action taken with these accounts should be logged. We explain what to record and how in our log article.

Types of DBA

The BLS describes two specializations:

  • System DBA: Responsible for the physical and technical aspects of a database, such as installing upgrades and patches to fix program bugs, and for making sure the database management systems work properly.
  • Application DBA: Does all the tasks of a general DBA but focuses on the database of a specific application, such as customer-service software. May write or debug programs.

The BLS also describes database architects separately: they design and build new databases for systems and applications. DBAs are distinguished by platform as well, as in Oracle DBA, SQL Server DBA or PostgreSQL DBA.

DBA vs a managed database service (DBaaS)

DBaaS means running the database as a service on a cloud provider. According to the comparison in the Amazon RDS documentation, with RDS the installation and patching of the operating system and the database software, backups, high availability and scaling all move to AWS. Application optimization stays with the customer in every model. AWS explicitly makes query tuning the customer's responsibility, because query performance depends on database design, data size and workload. Microsoft likewise describes Azure SQL Database as a PaaS database engine that handles most database management functions, such as upgrading, patching, backups and monitoring, without user involvement.

So DBaaS reduces the system side of the DBA's work but does not remove the application-facing part. A slowing query, a wrongly granted permission or a fast-growing table still needs someone's attention. We describe the model in which databases are run as a service on our managed platform services page.

When does outside DBA support make sense?

A year has 8,760 hours. A DBA working 40 hours a week covers 2,080 of them, or about 24%, even before vacation and public holidays. If the database sits behind a 24/7 service, on-call coverage cannot rest on one person. Outside support tends to make more sense when:

  • The organization does not have enough databases to keep a full-time DBA busy
  • After-hours on-call and holiday cover cannot be handled in-house
  • Infrequent but specialized work is coming up, such as major upgrades, migrations or high-availability setups
  • Several database engines exceed what one team can cover

The output to require in the contract is a regular restore test report. We cover the design of high-availability topologies and standard templates on our database platform engineering page.

Frequently asked questions

What does DBA stand for? Database administrator: the specialist responsible for installing, backing up, tuning and securing databases.

What does a DBA do day to day? A DBA installs and updates databases, takes backups and tests restores, finds slow queries, manages user permissions, and monitors replication and capacity.

What do you need to become a DBA? According to the BLS, database administrators usually have a bachelor's degree in an information- or computer-related subject. Certification is typically offered by software vendors or vendor-neutral certification providers.

Do you still need a DBA with a cloud database? With managed services, installation, patching and backups move to the provider, while query tuning and application optimization stay with you. The DBA's workload shrinks but does not disappear.

What is the difference between a DBA and a database architect? An architect designs and builds new databases; a DBA runs existing ones day to day. According to the BLS, experienced database administrators may advance to become database architects.

Sources