Skip to main content
EnglandComputer Science

AQA A-Level Computer Science 4.10 Fundamentals of databases: data modelling, normalisation, SQL and transactions

A deep-dive AQA A-Level Computer Science guide to 4.10 Fundamentals of databases. Covers conceptual data modelling and ER diagrams, relational databases with primary and foreign keys, normalisation to third normal form, SQL queries and data modification, and transaction processing with the ACID properties.

Generated by Claude Opus 4.817 min read4.10

Reviewed by: AI editorial process; not yet individually human-reviewed

Jump to a section
  1. What the databases topic actually demands
  2. Conceptual data modelling
  3. Relational databases and normalisation
  4. SQL
  5. Transaction processing
  6. Check your knowledge

What the databases topic actually demands

Databases are how large systems store structured data reliably. AQA expects you to model data, normalise to remove redundancy, write SQL to query and change data, and explain how transactions keep data consistent under concurrent access.

Conceptual data modelling

Identify the entities a system stores data about, their attributes, and the relationships between them, and draw an ER diagram labelled with the degree (one-to-one, one-to-many, many-to-many). A many-to-many relationship is resolved with a linking (junction) table, creating two one-to-many relationships.

Relational databases and normalisation

A relational database links tables by primary and foreign keys. Poor structure causes redundancy and update, insertion and deletion anomalies. Normalisation fixes this: 1NF removes repeating groups, 2NF removes partial dependencies, and 3NF removes transitive dependencies so every non-key attribute depends only on the primary key.

SQL

Retrieve data with SELECT ... FROM ... WHERE ... ORDER BY, combine tables with a join matching a foreign key to a primary key, and modify data with INSERT INTO, UPDATE ... SET and DELETE FROM, always using a WHERE clause to target the right records.

Transaction processing

A transaction is a single logical unit of work that must be all or nothing. The ACID properties (atomicity, consistency, isolation, durability) guarantee reliability. Record locking prevents lost updates but can cause deadlock, and redundancy and a transaction log allow recovery to a consistent state after a failure.

Check your knowledge

  1. State the difference between an entity and an attribute. (2 marks)
  2. Explain how a many-to-many relationship is resolved. (2 marks)
  3. State the purpose of a foreign key. (2 marks)
  4. State the condition a table must meet to be in third normal form. (2 marks)
  5. Write SQL to list the names of students with a mark above 60, highest first. (2 marks)
  6. State why a WHERE clause is essential in a DELETE statement. (1 mark)
  7. State what atomicity means in the ACID properties. (1 mark)
  8. Explain how a deadlock can arise from record locking. (2 marks)

Sources & how we know this

  • computer-science
  • a-level-aqa
  • aqa-computer-science
  • databases-and-sql
  • a-level
  • normalisation
  • sql
  • er-diagram
  • acid