A database is just a filing cabinet that can answer questions.

We'll start with drawers and folders — zero jargon. By the end, you'll be writing real queries and understanding how apps store and retrieve every piece of data you see.

No coding background needed
Interactive SQL you can try
Real-world analogies throughout
01

The Filing Cabinet

Before any technical terms: a database is a filing cabinet. It has labeled drawers, and inside each drawer are folders with the same kind of information.

Click a drawer to peek inside

Each drawer holds one kind of thing. All the folders inside follow the same format — same labels, different details.

How it maps

This filing cabinet is a database. Each drawer is a table. Each folder inside is a row. The labels on each folder are columns.

That's it. Everything else is just tools for opening drawers faster and smarter.
🗄️

Cabinet

The whole database. A collection of organized drawers (tables).

📂

Drawer

One table. Holds many folders (rows) of the same kind of thing.

📄

Folder

One row. A single record — one user, one order, one product.

🏷️

Label

A column. The name of a piece of info: name, email, city.

02

Your First Table

A table is really just a spreadsheet with stricter rules. Every column has a name, every row follows the same format. Click any row or column header to learn more.

users table 5 rows · 5 columns · Click anything to explore

Click a row or column

We'll explain what that piece of data means and how it maps to the filing cabinet analogy.

Mapping: Spreadsheet → Database

Spreadsheet tab"Sheet1" at the bottom
TableA named collection like "users"
Header rowName, Email, City…
ColumnsThe labels that define what data goes where
A row of dataOne person's info
Row (record)One entry in the table
A single cell"Emma Chen"
ValueOne piece of data at a specific column
03

The Four Operations

Everything you do with a database boils down to four actions. Developers call them CRUD — Create, Read, Update, Delete. Same four things you'd do with a filing cabinet.

Choose one operation above.
SQL

        
Result

        
04

Asking Questions

The most common thing you do with a database is ask questions. In SQL, that's called SELECT. Build a query by clicking the parts below — the results update live.

Visual Query Builder Click options in each row to construct your query
Show me
From
Where
Order by
Results
05

Relationships

Most databases have more than one table. The magic is how they connect. Think of it as two filing cabinets with a thread running between matching folders.

Click a user to see their orders light up The connection runs through user_id — every order knows which user placed it
👤 users
user_id
links to
🛒 orders
How JOINs work
When you click a user, you're mentally doing what SQL calls a JOIN — pulling matching data from two tables at once. The user_id column in orders is the thread connecting the two cabinets.
The JOIN query
SELECT users.name, orders.item, orders.price
FROM users
JOIN orders ON users.id = orders.user_id
-- Click a user above to see this filtered
JOIN Results
Click a user to see the joined data.
06

SQL Playground

Write any SQL query against the mock dataset. Try the preset buttons or type your own. The data resets each time you reload the page.

Output
Run a query to see results here.
📋 users id, name, email, city, joined
🛒 orders id, user_id, item, price, date
📦 products id, name, category, price
07

Glossary

All the terms from this guide in one place. Search or filter — and every term comes with a real-world analogy.

No terms match that search.