A database is an organized system for storing and managing data. Many applications you use every day rely on one: online stores keep users, products, and orders; schools keep students, courses, and grades; business systems may keep customers, employees, contracts, and financial records.
A spreadsheet, CSV file, or text file can be fine for a few dozen items. Trouble begins as the data grows, several people use it at once, or an application searches and updates it constantly. A database does more than “save” information: it gives that information a stable structure and provides reliable ways to find, change, and manage it.
Begin with one users table
In a relational database, data is usually stored in tables. A table resembles a spreadsheet because both have rows and columns. A database table, however, normally has a clearly defined structure: each column has a consistent meaning and data type.
| id | name | |
|---|---|---|
| 1 | Alice | alice@example.com |
| 2 | Bob | bob@example.com |
| 3 | Chris | chris@example.com |
Each column represents one kind of information: name stores a name and email stores an email address. Each row is one complete record. The highlighted row is the user Bob—not three unrelated values.
A useful mental model is: a table collects one kind of data, a row is one record, and columns define what every record contains.
Why split information into columns?
If user information is stored as one piece of plain text, a person may guess what each value means, but software cannot reliably know that the first part is a name and the second is an age. With fixed columns, “find every user in Tokyo” has a precise target: the city column. Updating Bob’s email only changes email, not the entire record.
| id | name | age | city | |
|---|---|---|---|---|
| 1 | Alice | 28 | Tokyo | alice@example.com |
| 2 | Bob | 31 | Osaka | bob@example.com |
One table usually stores one kind of data
Real projects rarely place everything in one giant table. They separate different kinds of data. An online store might have users, products, and orders for people, items, and purchases. Each table remains focused and can be maintained independently.
Columns and fields
You will also hear the word field. Developers say “the email field” or “add a status field.” Column is more precise when describing table structure; field is common in conversation and software interfaces. At this stage, you do not need to treat them as completely separate ideas.
A database is not database software
MySQL, PostgreSQL, and SQL Server are database management systems (DBMSs). They are software products that create, manage, query, and maintain data. A database is a particular collection of data managed by that software.
Think of Word and a Word document: Word is the editing software; a particular .docx file is the document. MySQL is management software; shop is a particular database.
KNOWLEDGE QUIZ
Meet common database products
Find three popular database management systems. For each, record whether it is a DBMS or a particular database, one common use case, and whether it is practical for learning on a personal computer. Do not simply copy marketing copy.
Next, we will use SQL to express “read, add, change, and remove” operations.