Y12 Normalisation - Workbook
Y12 Normalisation - Workbook
You can use ICT Lab,do research online or use your handbook to answer all
questions.
You can pair up or do this in groups – but every student need to upload this
booklet on his/her own.
• Each data item cannot be broken down any further i.e. it is ‘atomic’
• Each row/record is unique and has a primary key
• There are no records with repeating data
• Each field should be unique
Atomic data
Rule 1: Each data item cannot be broken down any further i.e. it is ‘atomic’
Buckingham Palace
Supersize cheeseburger
The records below have no primary key. Choose a suitable primary key and
complete the table.
The records below have no primary key. Choose a suitable primary key and
complete the table.
Table 1:
ID* Title Surname Telephone no
001 Miss Smith 01234 567890
002 Miss White 01234 890123
003 Miss James 01234 798453
004 Miss Green 01234 578345
Reason:
Table 2:
ID* Title Surname Full Name Telephone no
001 Mrs Field Mrs Field 01234 523645
002 Miss White Miss White 01234 890123
003 Mr Hancock Mr Hancock 01234 989654
004 Miss Green Miss Green 01234 578345
Reason
Table 3:
ID* Title Surname Email
001 Mrs Field [email protected]
Reason:
Table 1:
Reason:
Table 2:
Reason:
Remembering all of the rules of First Normal Form, identify which of the
following tables are in 1NF. Explain your reason
Example 1:
Reason:
Example 2:
Reason: .
Example 3:
Reason:
Example 4:
Reason:
Example 5:
Reason:
Example 6:
Reason:
Entity – Band
Entity – Fan
Each band has many fans. Each person is a fan of only one band.
Taking this information into account, draw the correct ER diagram below:
FAN
BAND
The The
attributes of attributes of
the band the fans
might be: might be:
Answer:
Answer:
The database designer finally comes up with the correct solution. He needs
to create a third table called EMAIL and use a foreign key in the fan table to
link to the primary key in the EMAIL table.
BA FA
EM
BAND
BandID*
FAN
FanID* FirstName
EMAIL
EmailID*
If it is not in 2NF, identify which non-key attribute does not depend on one of
the key attributes.
Answer:
CONCERT:
ARTIST:
STYLE:
PROJECT:
EmployeeID* ProjectID* DateHired ProjectManager
Does every non-key attribute depend on every key attribute? Explain your
answer
PROJECT:
PROJECTMANAGER:
COURSES:
CourseID* Term* PlacesAvailable CourseTitle
001 Autumn 50 Computing
001 Spring 40 Computing
001 Summer 45 Computing
002 Autumn 100 ICT
002 Spring 90 ICT
003 Summer 100 Robotics
Does every non-key attribute depend on every key attribute? Explain your
answer
No.
Course title is dependent on CourseID, but it has nothing to do with Term
COURSES AVAILABLE:
COURSE:
The table is in 2NF but it is not in 3NF because ‘Country’ could be derived
from ‘City’
City* Country
London UK
Birmingham UK
The new table called ‘countries’ has City as the primary key and ‘country’ as
an attribute.
The concert table has ‘city’ as a foreign key. Now there is no redundant data.
3NF – an example
COURSES AVAILABLE
TEACHER