20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
A typical day mixes routine checks and problem fixes. You start by monitoring database performance (CPU, queries, storage), review overnight backups, and check alerts from monitoring tools. Expect to tune slow queries, apply an urgent patch, or help a developer who broke a deployment.
Afternoons often include planning: capacity forecasting for growth, designing a new table or index, and writing runbooks for recovery steps. You also train users or junior staff and may join incident calls if a failure occurs.
Learn both relational and distributed systems. Start with a relational engine (MySQL, PostgreSQL) and one big distributed system listed above, like Apache Cassandra for wide-column stores and Apache Hive for big-data queries on Hadoop.
Also get comfortable with supporting tech: Apache Kafka for streaming data, Apache Airflow for job scheduling, and cloud basics like Amazon EC2. Knowing Ansible for automation and patching helps you manage many servers quickly.
You use Ansible to install database software, push security patches, and keep configuration consistent across nodes—so you don't hand-edit dozens of servers. Ansible reduces human error during upgrades and installs.
Airflow schedules and monitors ETL jobs, like loading data into Hive or triggering Cassandra repairs. Use Airflow for repeatable testing, backups, and recovery workflows so they run on time and you can replay failures.
According to the U.S. Bureau of Labor Statistics (BLS), about 69,990 people were employed as database administrators and database architects in 2025. The median pay was $104,620 per year, the lowest tenth earned $60,230, and the top tenth earned $163,320.
Salaries vary by location, experience, and technology (cloud or big-data roles often pay more). Use the BLS data above to set expectations for offers and negotiate.
A DBA focuses on installation, security, backups, tuning, downtime minimization, and recovery of databases (tasks like patching, indexing, and capacity planning). You manage the database as an operational service.
A data engineer builds data pipelines and transformations (using tools like Kafka and Airflow) and designs schemas for analytics. There’s overlap—DBAs often work with data engineers on Hive, Kafka, and Hadoop systems—but the DBA is responsible for availability and recovery.
You must be good at backups and recovery: perform and test full restores, use high-speed transaction recovery techniques, and minimize downtime. Practically, know how to run restores on replicas and validate data after failure.
Also master performance tuning (indexes, query plans), install and patch database software safely, and use monitoring and automation (Ansible, Airflow). Strong troubleshooting, reading logs, and writing clear runbooks for incident and problem management are essential.