In simple terms
A friendly intro before the formal notes — no formulas yet.
The Digital Library Catalogue
Databases are organised systems for storing, managing, and retrieving digital information, much like a library's catalogue organises books. They turn raw data into a powerful, searchable resource.
Imagine a library. The individual facts on each book's publication card (title, author, publication date) are 'data'. When you use the library's computer system to search for 'all books by George Orwell published after 1940', you are retrieving 'information'. The entire computer system, which holds all the book data and allows you to search, update, and manage it, is the 'database system'.
- 1
Start with raw facts, like a student's name and a book's title. This is 'data'.
- 2
Organise related data into tables with rows and columns, like a spreadsheet for students and another for books.
- 3
Link these tables using unique identifiers (keys), creating a 'relational database' to show who has borrowed which book.
- 4
Use a Database Management System (DBMS) as the software 'librarian' to control access, ensure data is consistent, and handle search requests.
Full topic notes
Formal explanation with the rigour you need for the exam.
From Raw Data to Structured Information
It's crucial to distinguish between 'data' and 'information'. Data consists of raw, unorganised facts. For instance, the number '16' is data. Without context, it's meaningless. Is it an age, a temperature, or a house number? When we process this data by giving it context—for example, 'Temperature: 16°C'—it becomes information. Databases are designed to store data in a structured way so that it can be easily processed into meaningful information.
Data: Raw facts without context.
Information: Data processed to have context, relevance, and purpose.
Database: A structured collection of data.
The goal of a database system is to transform data into useful information.
Organising Data: Relational Databases
While simple data can be stored in a single list or table (a flat-file database), this is inefficient for complex scenarios. Most modern systems use a relational database model. This model organises data into multiple tables, each focused on a single subject (like 'Students' or 'Courses'). These tables are then linked together using special fields called keys, which avoids duplicating data and ensures consistency.
Tables store data about a specific entity (e.g., customers, products).
Records (rows) represent individual instances of that entity.
Fields (columns) represent attributes of that entity (e.g., name, price).
Primary Keys uniquely identify each record in a table.
Foreign Keys link a record in one table to a record in another, forming a relationship.
Managing the Database: DBMS and SQL
A database doesn't manage itself. We use a Database Management System (DBMS), which is the software layer that sits between the users/applications and the physical database. The DBMS handles all interactions, from creating tables to running queries and enforcing security rules. To communicate our requests to the DBMS, we use a standardised language called Structured Query Language (SQL).
A typical SQL query to retrieve information looks like this:
SELECT Title, Director FROM Films WHERE ReleaseYear > 2000;
This command asks the DBMS to select the Title and Director columns from the Films table for all records where the ReleaseYear is after 2000.
In exam questions, especially in HL, you will be asked to apply these concepts to an unseen case study. Don't just define terms like 'Primary Key'. Instead, explain why a specific field in the case study's context would be a good primary key. For example, 'The ProductID would be a suitable primary key as it is guaranteed to be unique for each product, unlike the ProductName which could have duplicates.'
Worked examples
See the formulas applied — reveal one step at a time, like the exam.
A new streaming service wants to track its users and the films they watch. Design a simple relational database schema with two tables: Users and Films. Identify the fields for each table, a suitable Primary Key for each, and explain how you would track which user watches which film.
- 1
A good solution would involve three tables to correctly model the many-to-many relationship.
Using the streaming service database schema from the previous example (Users, Films, WatchLog), write an SQL query to find the titles of all films watched by the user with UserID = 15.
- 1
The solution requires joining the Films and WatchLog tables to link a user to a film title.
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
Key terms for this topic — skim now; the Check step will test them.
- Data
Raw, unprocessed facts and figures without context. For example, '1984', 'George Orwell', '978-0451524935'.
- Information
Data that has been processed, organised, structured, or presented in a given context so as to make it useful. For example, 'The book "1984" by George Orwell has the ISBN 978-0451524935'.
- Database
An organised collection of structured data, typically stored electronically in a computer system.
- DBMS (Database Management System)
Software that interacts with end users, applications, and the database itself to capture and analyse the data. Examples include MySQL, PostgreSQL, and Microsoft SQL Server.
- Relational Database
A type of database that stores and provides access to data points that are related to one another. Data is organised into tables (relations) which are linked by common fields.
- Flat-File Database
A database that stores data in a single table. This can lead to data redundancy and integrity issues for complex datasets.
- Primary Key
A field in a table that uniquely identifies each record in that table. It must contain unique values and cannot be null. For example, StudentID in a Students table.
- Foreign Key
A field in a table that is a primary key in another table. It acts as a cross-reference between tables to create a link. For example, StudentID in a Loans table would link to the Students table.
- SQL (Structured Query Language)
The standard programming language used to communicate with and manage relational databases.
- Data Redundancy
The unnecessary repetition of data in a database. Relational databases aim to minimise this. A common trap is designing a flat-file system where a customer's address is repeated for every order they make.
- Data Integrity
The maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle. DBMSs have built-in mechanisms to enforce this.
- Table (Relation)
A collection of related data held in a structured format within a database, consisting of columns (fields/attributes) and rows (records/tuples).
Name it
Read the meaning, then pick which of this lesson’s terms it describes. Miss one and you see what your choice really means.
Software that interacts with end users, applications, and the database itself to capture and analyse the data. Examples include MySQL, PostgreSQL, and Microsoft SQL Server.
Quick check
Write your answer first, then compare it with the model one — the gap is what you would have lost.
Teach it back
If you can explain it simply, you own it — gaps here are marks you’d lose.
Teach it back
Explain this topic as if teaching a friend. We name the gaps an examiner would still dock.
Revision flashcards
Guess first, then flip — retrieval beats re-reading.
Key takeaways
Review these before you close the topic — retrieval beats re-reading.
Data: Raw facts without context.
Information: Data processed to have context, relevance, and purpose.
Database: A structured collection of data.
The goal of a database system is to transform data into useful information.
Practice — then mark it
The whole point: a real Cambridge question, marked mark-by-mark.
Test your understanding of data, databases, and their societal impact with exam-style questions.
Test your understanding of data, databases, and their societal impact with exam-style questions.
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 understanding of data, databases, and their societal impact with exam-style questions. on paper, snap a photo, and get examiner-style feedback on exactly where you win and lose marks.
Discuss Data and databases
Ask, share and discuss with other Digital Society HL students
No posts yet — be the first to start the conversation.