Database Administrator job description and duties

Updated 17 September 2026 · 2 min read

A database administrator is responsible for the systems where an organisation's data actually lives. The role mixes planned work, such as patching and capacity planning, with urgent work when a database slows or stops. In smaller organisations it is combined with systems administration; in larger ones it is a specialism with its own team.

How this guide was made

Written for this site with AI assistance, then checked automatically before publishing. The topic table, sample questions, worked examples and study plan are generated from this site’s question bank: each worked example is recalculated by separate code, and each sample answer says where it came from.

The guide deliberately states no salaries, grades, pass marks or exam dates. Those change, and they could not be checked here, so take them from the advert itself.

This site is independent and is not affiliated with MIFOTRA or any employer.

Purpose of the role

The role keeps data correct, available to the people and systems entitled to it, protected from those who are not, and recoverable when something fails. Everything else follows from those four.

Installation and configuration duties

Install, configure and patch database servers.
Create databases, schemas and objects to agreed standards.
Configure storage, memory and connection settings for the workload.
Set up development, test and production environments consistently.
Document configurations and keep them current.

Performance duties

Administrators monitor query performance, investigate slow operations, maintain indexes and statistics, advise developers on query and schema design, and plan capacity so that growth does not become an incident. They are usually the last line of defence for a problem the application team cannot explain.

Backup, recovery and availability duties

Designing and running backup schedules against agreed recovery objectives, testing restores on a schedule, configuring replication or clustering, and leading recovery when a failure occurs. The role owns the runbook that makes recovery possible without the administrator present.

Security duties

Managing users, roles and privileges, applying least privilege, configuring encryption and auditing, reviewing access periodically, and handling sensitive data appropriately in non-production environments.

Change and release duties

Databases change constantly as the applications on top of them evolve, and the role applies those changes safely. That means checking scripts before they run, testing them against production-sized data, scheduling them where they disturb least, and keeping a way back when one misbehaves. In organisations with several environments, the administrator also keeps development and test databases close enough to production to be worth testing against, while making sure real personal data is not left sitting in either. The role is the last approval before a change reaches the data everyone depends on, which is why it appears in most release procedures.

Working relationships

Administrators work with application developers and vendors, systems and network administrators, the security team, and the business owners of each system. In organisations running national or shared systems, they also deal with the institutions that operate them.

How performance is judged

Availability of the databases, recovery tested and demonstrated, performance held as data grows, access controlled and reviewed, changes made without incident, and documentation good enough for someone else to follow.

Open adverts for this position

No open Database Administrator advert matched when the jobs board was last checked. It is refreshed every morning.

Browse every open vacancy

Common questions

Do database administrators work out of hours?

Often. Patching, migrations and maintenance are scheduled when the system is least used, and serious incidents do not wait for morning.

Is this role disappearing because of managed cloud databases?

It is changing rather than disappearing. Managed services remove some routine tasks and leave design, tuning, security, cost control and recovery planning firmly in the administrator's hands.