In simple terms
A friendly intro before the formal notes — no formulas yet.
From Filing Cabinet to Database
A database is a structured way to store and manage large amounts of related information electronically. It's far more powerful and efficient than a simple spreadsheet or a physical filing system.
Think of a library. A database is the entire library system. Each bookshelf is a 'table' (e.g., 'Books', 'Members'). Each book on the shelf is a 'record'. The details on the book's spine like 'Title' and 'Author' are the 'fields'. The unique library card number for each member is a 'primary key' that ensures no two members are confused.
- 1
Identify the main 'things' (Entities) you need to store data about, like 'Student' or 'Course'. Each entity becomes a table.
- 2
For each entity, list the specific pieces of information (Attributes) you need to store, such as 'StudentID' or 'CourseName'. These become the fields in your table.
- 3
Establish how the tables are connected (Relationships). For example, a 'Student' enrols in many 'Courses'.
- 4
Assign a Primary Key to each table to uniquely identify every record, like a 'StudentID', and use Foreign Keys to link the tables together.
Explore the concept
Use the live diagram and synced steps — play it or tap a step card to walk through.
Full topic notes
Formal explanation with the rigour you need for the exam.
The Relational Database Model
The most common type of database you'll encounter is the relational database. It organises data into one or more tables of columns and rows, with a unique key identifying each row. The 'relational' part comes from the ability to link these tables together, allowing you to see the relationships between different pieces of data.
A table represents an entity (a 'thing' we store data about, e.g., 'Car').
A row represents a record (a specific instance of that entity, e.g., a specific Ford Focus).
A column represents a field or attribute (a characteristic of the entity, e.g., 'Colour' or 'EngineSize').
Creating Links: Keys and Relationships
The real power of relational databases is not just storing data, but connecting it. This is achieved using keys. A Primary Key is a field that uniquely identifies every record in a table. Think of it as a National Insurance number or a student ID; no two people have the same one. A Foreign Key is a primary key from one table that is placed into another table to create a link. For example, if we have a Tutor table and a Student table, we can place TutorID into the Student table to show which tutor is assigned to which student.
One-to-One (1:1): Each record in Table A relates to exactly one record in Table B. E.g., one Country has one CapitalCity. This is rare.
One-to-Many (1:M): One record in Table A can relate to many records in Table B. E.g., one Author can write many Books.
Many-to-Many (M:M): Many records in Table A can relate to many records in Table B. E.g., many Students can enrol in many Courses. This requires a special 'linking table' to implement.
Examiners frequently ask about resolving a many-to-many relationship. Remember the rule: you must create a new 'linking' table in between the two original tables. This linking table will contain foreign keys from both original tables, which together will often form a composite primary key.
The Database Management System (DBMS)
It's important not to confuse the database with the Database Management System (DBMS). The database is the data itself, stored in files. The DBMS is the complex software that acts as an intermediary, allowing users and applications to interact with the database without needing to know the low-level details of how the data is physically stored. It manages everything from security and access rights to ensuring data integrity and handling simultaneous user requests.
Data Definition: The DBMS provides a Data Definition Language (DDL) to define the database schema (tables, fields, keys).
Data Manipulation: It provides a Data Manipulation Language (DML), like SQL, to insert, update, delete, and query data.
Security: Manages user accounts and access permissions.
Data Integrity: Enforces rules to maintain the accuracy and consistency of data.
Concurrency Control: Manages simultaneous access by multiple users to prevent conflicts.
Backup and Recovery: Provides tools to back up data and recover from system failures.
Worked examples
See the formulas applied — reveal one step at a time, like the exam.
A vet clinic needs a simple database to keep track of pets. (a) Identify the main entity. (b) Suggest four suitable attributes for this entity, and state an appropriate data type for each. (c) Draw a table structure and provide one example record.
- 1
(a) The main entity is 'Pet'. [1 mark]
A college database has a TblStudent and a TblCourse. A student can enrol on many courses, and a course can have many students. (a) What type of relationship exists between TblStudent and TblCourse? (b) How would this relationship be implemented in a relational database? Name the table(s) and key fields required.
- 1
(a) This is a many-to-many relationship. [1 mark]
How it all connects
The big idea sits in the middle — tap a linked idea to explore the link.
Tap a linked idea to see how it connects back to the main topic — that connection is what examiners reward.
Glossary
Try to recall each definition before you reveal it.
Quick check
Answer in your head first — then tap to check. No pressure.
Revision flashcards
Flip the card. Test yourself before the exam.
What is a database?
A persistent, organised collection of structured data, typically stored and accessed electronically from a computer system.
Key takeaways
Review these before you close the topic — retrieval beats re-reading.
- ✓
A table represents an entity (a 'thing' we store data about, e.g., 'Car').
- ✓
A row represents a record (a specific instance of that entity, e.g., a specific Ford Focus).
- ✓
A column represents a field or attribute (a characteristic of the entity, e.g., 'Colour' or 'EngineSize').
Practice — then mark it
The whole point: a real Cambridge question, marked mark-by-mark.
Test Your Knowledge on Database Concepts
Test Your Knowledge on Database Concepts
Extra simulations & links
PhET, GeoGebra and other curated tools — open in a new tab.
Frequently asked
Checkpoint
One marked question is worth ten re-reads — close the loop before you move on.
Reading it isn’t knowing it — prove it.
Before you move on: do Test Your Knowledge on Database Concepts on paper, snap a photo, and get examiner-style feedback on exactly where you win and lose marks.