Relational Databases Normalisation

4.10.3 (11 questions). Public Notes: AQA's A Level Computer Science

Why must all databases be fully normalised?

  1. No duplication of data leads to…
    1. Easier to update and change data, as changes will only need to occur in one field.
    2. Maintaining data integrity, and removes the possibility of one record having two different values for attributes.

  2. Having smaller tables with fewer fields...
    1. Means faster queries.
    2. Means more data can fit inside the same amount of space

What causes non-atomic fields?

Many-to-Many relationships.

How to resolve non-atomic fields?

Split an entity into two relations.

What causes repeating groups of attributes?

Many-to-many relationships.

How to resolve repeating sets of attributes?

Introduce link tables.

Describe a link table?

A relation with all of the attributes being both foreign keys of other relations and composite primary keys of itself.

What is a partial key dependency?

Where an entity has a composite primary key and another attribute is dependent on only one of the attributes that make up the primary key.

What is a non-key dependency?

Where an attribute is not dependant on the primary key.

What is 1st normal form (1NF)?

  1. No-non atomic fields.
  2. No repeating sets of data.

What is 2nd normal form (2NF)?

  1. No-non atomic fields.
  2. No repeating sets of data.

  3. No partial key dependencies.

What is 3rd normal form?

  1. No-non atomic fields.
  2. No repeating sets of data.

  3. No partial key dependencies.

  4. No non-key dependencies.