Mostly harmless, conspicuously useful

The Hitchhiker's Guide to Becoming a Database Administrator

A database administrator keeps an organisation's stored facts available, correct, recoverable, and visible only to the right people, which databases appreciate because they are literal-minded institutions: they will preserve a typo for twenty years if properly instructed. You learn to read schemas and query plans, manage locks and privileges, prove restores, rehearse failover, and lead incidents where several calm adults discover that the green backup badge was merely expressing an opinion. This guide raises the stakes in a safe order, using plans, logs, recovery timings, audit records, and drills to distinguish durable service from a catastrophe wearing a reassuring dashboard.

Level 1 · Novice

Read the schema before asking the orders table to recount civilisation

You inspect schemas and SQL without changing data, learning how a perfectly polite query can tour every row, consume the afternoon, and return exactly what you requested rather than what you meant.

You begin with read-only artifacts: a schema diagram, table definitions, sample rows, saved SQL queries, and an execution plan showing how the database intends to find an answer. A schema is the organised blueprint of tables, columns, relationships, and rules; the database treats those rules like a diligent clerk who has never heard the phrase “you know what I meant.” You review the map with developers, analysts, support staff, and an experienced administrator so everyone can trace how customers, orders, and payments connect before anyone moves a wall that turns out to be load-bearing.

Suppose checkout slows after a release. In a test environment or read-only replica, you copy the exact checkout query, request only the needed columns, add a sensible result limit, and inspect its execution plan without altering production data. You record elapsed time, estimated and actual row counts, and whether the plan reads the entire orders table as though searching every filing cabinet for one receipt. That evidence lets a developer fix an over-broad filter or escalate an indexing problem; one brisk laptop result is an anecdote with good posture, not a diagnosis.

Words from the spaceship manual, translated

Schema: The database blueprint naming tables, columns, relationships, and validity rules; it is the institution's constitution, except invalid values are refused immediately rather than debated in committee.
Query: A structured request to retrieve or change information; the database follows its wording with magnificent literalism, so beginners must distinguish reading statements from data-changing ones.
Execution plan: The database's proposed route through tables, indexes, and joins to answer a query, rather like an itinerary that reveals a planned twelve-million-row scenic detour before departure.