Databases for Beginners
by Sergey Okinchuk
Ch. 1

Databases for Beginners

Welcome

Almost everything you do online — ordering food, booking a seat, logging in — ends in a database, and almost nobody outside engineering can say what one actually is. This course fixes that properly. It teaches what a database is and why spreadsheets stop being enough, how tables model the real world, and how to read and write real SQL — actual queries, shown on the page, with nothing to install. Then the ideas that make databases trustworthy and fast: design, constraints, transactions, indexes. By the end you can read a real query, follow any schema, and hold your own in a "Postgres or Mongo?" conversation — with reasons.

11 chapters 51 topics covered 7 hours audio Knowledge check on every topic

About This Course

Databases carry a strange reputation: everyone agrees they matter, and most explanations either drown you in theory or hand you a wall of syntax to memorize. Meanwhile the actual subject is concrete and surprisingly friendly — a database is a tool for keeping shared data structured and trustworthy, and SQL, the language for talking to it, reads closer to English than any other thing in computing. This course teaches both, honestly and from zero.

To keep it concrete, the whole book follows one small business. Marquee is a two-screen neighborhood cinema run by Lora, who starts the course managing films, showtimes, and bookings in a spreadsheet — and outgrows it by the end of Chapter 1. Chapter by chapter, the Marquee's data becomes a real database: tables in Chapter 2, questions and answers in Chapters 3 and 4, safe changes in Chapter 5, honest design in Chapter 6, bulletproof seat booking in Chapter 7, speed in Chapter 8, and a live website in Chapter 9. Every idea in the book lands on data you already know.

This is a hands-in-the-code course with nothing to install. Real SQL appears on almost every page — actual queries against the Marquee's tables — and every query is also explained in plain words, so you can read the book on a phone on a train and lose nothing. If you want to type along, any free online SQL playground works; the course never depends on it.

Who This Is For

Anyone who works next to data and wants to actually understand it: career-switchers heading toward engineering or analytics, students who want the ideas before the jargon, managers and product people who keep hearing "we'll need to change the schema" in meetings, and analysts tired of asking someone else to pull the numbers. It assumes no engineering background at all — only everyday computer literacy. If you administer databases for a living, this course is below you; if the word "database" has always been a black box, it was built for exactly you.

What You Should Already Know

  • How to use a computer, a browser, files, and folders as an everyday user — nothing more technical than that
  • No programming and no command line — every piece of SQL is introduced from zero and read aloud in plain words
  • No prior database exposure — every term is defined the first time it appears
  • Having seen a spreadsheet helps, because Chapter 1 is about where spreadsheets break

How the Course Is Built

The eleven chapters build in a deliberate order. First the why — the specific failures that make files and spreadsheets stop being enough. Then the relational model: tables, keys, and how facts point at each other. Two chapters teach reading data — SELECT, filters, groups, and the JOINs that reassemble split data into answers — and one teaches changing it without disasters. Then the craft: designing a database that cannot contradict itself, transactions that make changes all-or-nothing, and indexes that make millions of rows answer in milliseconds. Chapter 9 connects it all to real applications — including the one security lesson every beginner should hear early. The last two chapters widen the map: the NoSQL families, told honestly, and a working framework for choosing a database. The final page is an honest list of where to go next.

Every topic has the same gentle shape: a hook from Lora's cinema to start, the idea built step by step, the real SQL shown and then said in words, one everyday comparison to make it stick, the mix-ups people usually run into, why it matters, and a short knowledge check. It is patient, but it keeps moving — you are here to learn, not to be slowed down.

Real SQL, nothing to install
Actual queries on every page, always explained in plain words beside the code. The book works as a book; a playground is optional, never required.
One cinema, all the way through
The Marquee's four tables — films, screenings, customers, bookings — accumulate through every chapter, so each new idea lands on data you already know by heart.
Honest, never hyped
Relational by default, NoSQL when a specific reason says so — and every tool's tradeoffs stated plainly. Nothing you will have to unlearn later.
Concepts that travel
Engines and version numbers churn; tables, keys, transactions, and indexes don't. Learn the model once and every database you ever meet — Postgres, MySQL, SQLite — speaks it.

Chapter Map

Chapter 1
Why Databases Exist
The Saturday two volunteers sell the same seat twice, the database and its bodyguard the DBMS, the cinema we'll follow all book, and the honest map of the database families.
Chapter 2
Tables and the Relational Model
Tables as declared shapes, data types and the strange case of NULL, primary keys that name every row, foreign keys that point — and the junction table where the real business lives.
Chapter 3
Reading Data — SELECT
Questions become queries: SELECT and WHERE, sorting and top-fives, values computed on the fly, and the GROUP BY behind every dashboard number you have ever seen.
Chapter 4
Combining Tables — JOINs
Split data reassembled into answers: INNER JOIN, LEFT JOIN and the art of seeing what's missing, four-table questions built one step at a time, and queries inside queries.
Chapter 5
Changing Data
INSERT, UPDATE, and DELETE — including the most famous mistake in all of SQL, staged in slow motion — plus soft deletes and moving 800 rows at once with CSV.
Chapter 6
Designing a Good Database
Turning a business into tables, normalization without the jargon, constraints that make bad data impossible, when bending the rules is engineering — and how schemas change safely.
Chapter 7
Transactions and Safety
Two seats, together or not at all: transactions, ACID in plain words, what happens when two people want seat G7 in the same second, and the only real undo — backups.
Chapter 8
Making It Fast — Indexes
Why queries slow down as data grows, the sorted structure that turns forty thousand checks into three hops, what every index costs on every write, and asking the planner directly.
Chapter 9
Databases in Real Applications
Who actually runs your SQL, the injection attack every beginner should meet early, accounts and least privilege, where databases physically run, and the code that writes SQL for you.
Chapter 10
Beyond Relational — NoSQL
Why other database families exist and what each gives up: documents, key-value stores and caches, search engines, wide-column stores, and graphs — told without hype or dismissal.
Chapter 11
Choosing and What's Next
A working framework for choosing a database, honest portraits of the engines you'll hear about, the OLTP/OLAP split behind the analytics world, and where to go from here.

Disclaimer

This course is an independent educational project created and maintained by Sergey Okinchuk. It is provided for learning and reference purposes only.

No affiliation. This course is not affiliated with, sponsored by, endorsed by, or officially connected to any company, product, or organization mentioned. All opinions, interpretations, and recommendations expressed are those of the author. Marquee and all characters in this course are fictional; any resemblance to real companies or persons is coincidental.

Trademarks. Product and company names referenced are the property of their respective owners. Use of these names is for identification and educational purposes only and does not imply any endorsement.

Educational simplifications. This material teaches durable concepts for understanding, not operational instructions. Explanations are deliberately simplified for learning; where a simplification could mislead, the text flags it. This course is not professional advice, and is not a substitute for qualified expertise in any decision involving database systems.

Accuracy and currency. Databases evolve — engines, versions, and practices drift over time. Facts in this course reflect the author's understanding at the time of writing and may not be current. The course deliberately teaches the durable relational model and standard SQL rather than product specifics; always consult authoritative sources for the current state of any engine.

No warranty. This material is provided "as is" without warranty of any kind. The author accepts no liability for any loss or damage arising from reliance on the content.