Database design — relational schemas, normalisation
T-Level: Digital Production, Design & Development: Database design — relational schemas, normalisation
What you'll learn
- 1
Think of a messy spreadsheet with customer orders — the same customer's name appears 10 times! That's a data nightmare. 😱
- 2
Why is it bad to have the same customer name repeated many times in an orders table?
- 3
Let's normalise this orders table together: OrderID, CustomerName, CustomerAddress, ProductName, Price
- 4
Drag each column name into the correct table: Customer table or Orders table
- 5
What is the foreign key in the Orders table that links to the Customer table?
- 6
Normalisation also removes partial dependencies — where a column depends on only part of a composite key.
- 7
In this table: (OrderID, ProductID, ProductName), which column is partially dependent on ProductID?
Practise Database design — relational schemas, normalisation with Whizlo
Free AI-tutored lessons, unlimited practice questions, and progress tracking for ages 16–18. Aligned to the UK National Curriculum.