RDBMS Concepts Explained
In this lesson: Core RDBMS concepts — relation, tuple, attribute, domain, keys and integrity — explained with one example table.
What is an RDBMS
An RDBMS (Relational Database Management System) is a DBMS that stores data in tables and lets those tables relate to each other using keys. This relational model is simple yet powerful, and it is why MySQL, PostgreSQL and Oracle are so widely used.
Tables, rows and columns
A table holds data about one kind of thing (like students). Its parts:
- Column — a field such as
nameormarks; defines the data type. - Row — one record, e.g. one student, with a value for each column.
| roll | name | marks |
|---|---|---|
| 1 | Aman | 88 |
| 2 | Diya | 92 |
Here roll, name, marks are columns; each line is a row.
Keys in short
- Primary key — uniquely identifies each row (like
roll); never null, never repeated. - Foreign key — a column that links to another table's primary key.
- Unique key — values must all differ, but it can allow one null.
Keys keep data correct and let tables connect. We cover them in depth in their own lessons.
How tables relate
The power of an RDBMS is linking tables. A foreign key in one table points to the primary key of another:
students(roll PK, name) marks(id PK, roll FK -> students.roll, subject, score)
Here marks.roll links each mark to a student. This avoids repeating student details in every mark row.
DBMS vs RDBMS
| Point | DBMS | RDBMS |
|---|---|---|
| Data stored as | Files or various forms | Tables (relations) |
| Relationships | Usually none | Yes, via keys |
| Constraints | Limited | Keys, constraints enforced |
| Examples | File-based systems | MySQL, Oracle |
A worked example
Imagine a shop. Instead of one giant messy table, an RDBMS splits data:
customers— id, name, city.orders— id, customer_id (FK), amount.
Each order stores only a customer_id, not the full customer details. To see a customer's orders, the RDBMS joins the two tables on that key — no duplication, always consistent.
Common mistakes
- Repeating data across rows. Split into related tables instead.
- No primary key. Every table should have one to identify rows.
- Confusing row and column. Columns are fields; rows are records.
- Thinking DBMS and RDBMS are identical. RDBMS adds tables, keys and relationships.
Summary
- An RDBMS stores data in tables and links them with keys.
- Columns are fields; rows are records.
- A primary key uniquely identifies each row.
- A foreign key connects one table to another.
- The relational model avoids duplication and keeps data consistent.
Next, learn the wider picture in the DBMS tutorial, or keys in DBMS keys explained.
