Back to marketplace

4.3 Relational Databases and Normalisation

No description yet. This curated deck is ready for daily study.

Total cards: 7•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (7)

#1
Front (Question)

Relations

Back (Answer)

Where data is held in tables in a relational database

#2
Front (Question)

Normalisation

Back (Answer)

• A process used to come up with the best possible design for a database • Tables should be organised so that data is not duplicated in the same table or in indifferent tables • The structure should allow complex queries to be made

#3
Front (Question)

3 stages of normalisation

Back (Answer)

1NF, 2NF, 3NF

#4
Front (Question)

1NF

Back (Answer)

• Contains no repeating attributes or groups of attributes • All attributes must be atomic - a single attribute cannot consist of 2 data items such as firstname and surname

#5
Front (Question)

2NF

Back (Answer)

• 1NF and contains no partial dependencies • Can only occur if the primary key is a composite key

#6
Front (Question)

3NF

Back (Answer)

Contains no non-key dependencies

#7
Front (Question)

Advantages of normalisation

Back (Answer)

• Easier to maintain and change • No unnecessary duplication of data • Data integrity is maintained • Having smaller tables with fewer fields means faster searches and savings in storage