Unit Overview
Databases
CIE A-Level Computer ScienceΒ· 5 min read π n/a
1. Unit at a glance
We start with the big picture of why databases exist, what problems they solve compared to unstructured or flat-file storage, before moving into the dominant relational database model that powers most modern applications. Next, we cover how to implement and interact with databases using Structured Query Language (SQL), the global standard for relational data work.
We then cover the critical process of database normalisation to eliminate data redundancy and protect data integrity, before moving to advanced topics including distributed database architectures and transaction management for multi-user systems. Each topic builds incrementally on the previous one, moving from core concepts to practical design and advanced system management.
This unit is split into the following linked sub-topics:
Database concepts
Introduces core terminology, the limitations of flat files, and the purpose of modern database systems.
β β± 8 min
Relational database model
Covers entities, attributes, relationships, keys, and entity-relationship (ER) diagram design.
β β β± 10 min
Structured Query Language (SQL)
Teaches writing SQL for table creation, querying with filters/joins, and data manipulation.
β β β β± 15 min
Normalisation
Explains functional dependencies and how to normalise databases up to Third Normal Form (3NF).
β β β β β± 12 min
Client-server and distributed databases
Compares different database architectures and the core properties of distributed database systems.
β β β β± 9 min
Transactions and concurrency control
Covers ACID properties and mechanisms to prevent conflicts from concurrent database access.
β β β β β± 10 min
2. Common Pitfalls
Wrong move:
Confusing primary keys and foreign keys when designing relational tables
Why:
This leads to incorrect joins and broken relationships between entities, costing marks in exam questions
Correct move:
Remember: primary keys uniquely identify a row in a table, while foreign keys reference a primary key in another table
Wrong move:
Skipping all four ACID properties when answering exam questions on transactions
Why:
Most exam mark schemes require all four properties to award full marks
Correct move:
Memorise Atomicity, Consistency, Isolation, Durability and the definition of each property
Wrong move:
Believing all databases must be normalised to 3NF in every case
Why:
Over-normalisation causes unnecessary performance overhead for read-heavy applications
Correct move:
Normalise to 3NF for most designs, but recognise when denormalisation is appropriate for performance
3. Quick Reference Cheatsheet
Key Concept | Description |
|---|---|
Primary Key | Unique attribute that identifies each individual row in a relation |
Foreign Key | Attribute that references the primary key of another relation to link entities |
Third Normal Form (3NF) | No transitive functional dependencies; all non-key attributes depend only on the primary key |
Core SQL structure to query and combine data from multiple related tables | |
ACID Properties | Atomicity, Consistency, Isolation, Durability: required for reliable transaction processing |
Client-Server Architecture | Centralised database stored on a server, accessed by multiple client devices over a network |
What's Next
Start with the first sub-topic to build your foundational understanding of database concepts, then work through the sequence to master design, implementation, and advanced management. Once you complete all sub-topics in this unit, you will move on to the next unit covering software engineering principles. Let's get started.