Books › Database Administrator roadmap
Best books for Database Administrators (DBAs)
From relational basics to running databases reliably. The opening books cover SQL, database design, common mistakes and MySQL. The build set covers PostgreSQL, MySQL performance, query optimisation and SQL Server internals. The lead set covers reliability engineering, how storage engines work, distributed data systems and data management.
12 books in 3 stages, about 4,900 pages (at least 123 hours of reading). The notes are ours, with no ratings or sales claims.
How to choose your books
A short method, so you read the right book for where you are instead of the longest list.
Find your stage
Getting started · 4 books
Relational fundamentals: querying, designing tables well, avoiding common mistakes and a first database system.
Jump to this stage ↓Doing the job · 4 books
Running a database properly: PostgreSQL, MySQL performance, query optimisation and SQL Server internals.
Jump to this stage ↓Senior and leading · 4 books
Reliability and depth: running databases as services, how storage engines work, distributed data and data management.
Jump to this stage ↓
If you are unsure, start one stage lower than you think. Books in a later stage assume the working knowledge the earlier ones give you.
Begin with one book
Our starting pick
Learning SQL: Generate, Manipulate, and Retrieve Data
by Alan Beaulieu · 2005
Everything a DBA tunes, secures and backs up exists to serve queries. Solid SQL is the base.
See the book ↓Then pick by your situation
Choose the next book by the problem in front of you, not by its place in the list.
If your schema design feels ad hoc
read Database Design for Mere Mortals, 4th Edition (getting started)
If queries are slow and you need a method for fixing them
read PostgreSQL Query Optimization (doing the job)
If you want to understand what a database does internally
read Database Internals (senior and leading)
Check it against what Database Administrator postings ask for
These skills come from our analysis of live Database Administrator job postings. If one is new to you, its book list sits one click away.
Each step on the scale reflects how often live job postings name the skill, tool or credential, based on our analysis of those postings. With fewer than 100 postings behind this page, treat the scale as directional: a sample this size can shift a skill by a step or more.
Set a time budget
| Stage | Books | Pages | Reading | At 3 hrs a week |
|---|---|---|---|---|
| Getting started | 4 | ≥ 1,250 | ≥ 31 hrs | ≥ 10 wks |
| Doing the job | 4 | ≥ 1,870 | ≥ 47 hrs | ≥ 16 wks |
| Senior and leading | 4 | 1,780 | 45 hrs | 15 wks |
| All 3 stages | 12 | ≥ 4,900 | ≥ 123 hrs | ≥ 41 wks |
Treat this as a ceiling, not a target. Read one book at a time, apply it, then move on; read reference-style books in sections. Totals are approximate.
Judge any book before you buy it
Age
This list runs from 1996 (Database Design for Mere Mortals, 4th Edition) to 2023 (Mastering PostgreSQL 15). Older books earn their place by teaching principles that do not change. For tools and platforms, buy the latest edition.
Level
Check the stage before the title. A book from a later stage will make sense only once you have faced the problems it solves.
Format
The longest book here, Pro SQL Server Internals, 2nd Edition, runs about 800 pages. Read very long books as references: pick the chapter that matches the problem you have.
Fit
Ask what you will do differently the week after you finish. If you cannot answer, the book is for a different moment. Come back to it when the situation arrives.
Getting started
Relational fundamentals: querying, designing tables well, avoiding common mistakes and a first database system.
Start hereLearning SQL: Generate, Manipulate, and Retrieve Data
by Alan Beaulieu · 2005
~380 pages~10 hrs to read
Teaches queries, joins, grouping, subqueries and data modification from scratch with clear examples. SQL is the daily language of the job, so work through it early.
View book →Database Design for Mere Mortals, 4th Edition
by Michael J. Hernandez · 1996
A database-agnostic method for turning business requirements into tables, keys and relationships. Read it before you take over any schema, because bad design is the root of many later performance problems.
View book →
SQL Antipatterns: Avoiding the Pitfalls of Database Programming
by Bill Karwin · 2010
~320 pages~8 hrs to read
Catalogues common mistakes in schema design, queries and application access, with fixes. Read it early to spot problems in the schemas and queries developers hand you.
View book →
Learning MySQL: Get a Handle on Your Data
by Vinicius Grippa, Sergey Kuzmichev · 2021
~550 pages~14 hrs to read
Covers installing, configuring and operating MySQL 8, including replication, backup and basic tuning. Read it if MySQL is part of the stack you will be running.
View book →
Doing the job
Running a database properly: PostgreSQL, MySQL performance, query optimisation and SQL Server internals.
Mastering PostgreSQL 15
by Hans-Jürgen Schönig · 2023
~520 pages~13 hrs to read
Covers indexing, query planning, transactions, replication, backup and security in PostgreSQL. Read it when you are responsible for a production Postgres instance.
View book →
High Performance MySQL: Optimization, Backups, and Replication, 4th Edition
by Silvia Botros, Jeremy Tinley · 2004
~550 pages~14 hrs to read
Covers schema and index design, query tuning, replication, backups and operations on MySQL at scale. Read it when you are tuning real workloads.
View book →PostgreSQL Query Optimization: The Ultimate Guide to Building Efficient Queries
by Henrietta Dombrovskaya, Boris Novikov, Anna Bailliekova · 2021
Explains how the PostgreSQL optimizer picks plans, how to read them and how to fix slow queries through indexes and rewrites. Read it when slow queries land on your desk.
View book →
Pro SQL Server Internals, 2nd Edition
by Dmitri Korotkevitch · 2014
~800 pages~20 hrs to read
Covers SQL Server storage, indexes, locking, concurrency and query execution in depth. Read it when you administer SQL Server and need to diagnose performance, not just apply tips.
View book →
Senior and leading
Reliability and depth: running databases as services, how storage engines work, distributed data and data management.
Database Reliability Engineering: Designing and Operating Resilient Database Systems
by Laine Campbell, Charity Majors · 2017
~290 pages~7 hrs to read
Applies reliability engineering to databases: service levels, infrastructure, automation, backup and recovery, and migrations. Read it when you move from tending servers to designing how they are run.
View book →
Database Internals: A Deep Dive into How Distributed Data Systems Work
by Alex Petrov · 2019
~280 pages~7 hrs to read
Explains storage engines, B-trees and LSM trees, then distributed concerns such as replication, consensus and transactions. Read it when you choose or design database platforms.
View book →
Designing Data-Intensive Applications
by Martin Kleppmann · 2017
~620 pages~16 hrs to read
Explains storage engines, replication, partitioning, transactions and stream and batch processing, and the trade-offs between them. Read it when you design the systems that data and models run on.
View book →
DAMA-DMBOK: Data Management Body of Knowledge, 2nd Edition
by DAMA International · 2009
~590 pages~15 hrs to read
A broad reference on data governance, architecture, security, quality, metadata and operations. Useful for senior DBAs and architects who set standards beyond a single database.
View book →
Book links go to Amazon and are affiliate links. As an Amazon Associate I earn from qualifying purchases.
Frequently asked questions
Which book should a Database Administrator read first?
Learning SQL: Generate, Manipulate, and Retrieve Data by Alan Beaulieu. Everything a DBA tunes, secures and backs up exists to serve queries. Solid SQL is the base.
Do I need to read all 12 books?
No. The list is a menu, not a syllabus. Find your stage (getting started: 4, doing the job: 4, senior and leading: 4), begin with one book (we suggest Learning SQL: Generate, Manipulate, and Retrieve Data), then pick the next book by the problem you are facing at work. Come back to the others when the situation they cover arrives.
How long does it take to read these books?
The 10 books with a known page count add up to about 4,900 pages, roughly 123 hours at 1.5 minutes a page. At three hours a week that is about 41 weeks; at six hours a week, about 21. The list is meant to be read over time, one book at a time, not in one run.
Are these books up to date?
They range from 1996 (Database Design for Mere Mortals, 4th Edition) to 2023 (Mastering PostgreSQL 15). Older titles are included because they teach principles that have not changed; for tools and platforms, we favour recent editions. Check the edition before you buy.
Related reading
Some links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not change what we list.