What data is and why we store it in tables

How it all began

While GadgetHub was tiny, the founder jotted products straight into a notepad:

Looks like it's all there. But try to answer quickly:

• How much does the Powerbank cost? 35 and 5 — which is the quantity and which is the price?
• Which products have fewer than 10 left?
• How many products are in the store altogether?

Hard, isn't it? The price runs into the name, the quantity is sometimes in front and sometimes behind, two products share one line. This is data — facts about products — but without structure it's almost useless.

What data is

Data is facts about something real: a product, a customer, an order. On its own, the fact "59" says nothing. But "the price of the headphones is $59" — now that's useful. Data comes alive once it's clear what each fact means.

The solution — a table

Let's sort that same mess onto shelves:

Feel the difference? Now:

• columns — the attributes: name, price, stock, the same for every product;
• rows — the individual products: one row = one product with all of its data.

And the answers become instant: the powerbank's price is in its row; what's low in stock — you check the stock column; how many products — as many as there are rows.

The key idea

A table turns chaos into structure: facts of the same kind line up one under another, so they're easy to count, search, and compare. Every relational database is built from tables just like this one — and you've just taken your first step toward it.