Scribd
Upload
148 views11 pages

Normalisation in MS Access

The document discusses database normalization and its goals. Normalization is achieved by following a set of rules called normal forms. The three normal forms are: 1) First normal form requires rows to be unique and values atomic. It addresses issues like duplicate rows. 2) Second normal form requires the database to be in 1NF and attributes to be fully dependent on the primary key. It addresses non-key attributes that depend on only part of a composite primary key. 3) Third normal form requires the database to be in 2NF and for attributes to not be transitively dependent on the primary key via another non-prime attribute. It addresses attributes whose values are determined by other attributes rather than the primary key.

Uploaded by

Frances Vorster
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
148 views11 pages

Normalisation in MS Access

The document discusses database normalization and its goals. Normalization is achieved by following a set of rules called normal forms. The three normal forms are: 1) First normal form requires rows to be unique and values atomic. It addresses issues like duplicate rows. 2) Second normal form requires the database to be in 1NF and attributes to be fully dependent on the primary key. It addresses non-key attributes that depend on only part of a composite primary key. 3) Third normal form requires the database to be in 2NF and for attributes to not be transitively dependent on the primary key via another non-prime attribute. It addresses attributes whose values are determined by other attributes rather than the primary key.

Uploaded by

Frances Vorster
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Normalisation in MS Access

What is Normalisation?
• The words normalization and normal form refer to the structure of a database
• Normalization increases clarity in organizing data in Databases
• Normalization of a Database is achieved by following a set of rules called 'forms' in creating the
database
• Database normalization is a database schema design technique, by which an existing schema is
modified to minimize redundancy and dependency of data. Normalization split a large table into
smaller tables and define relationships between them to increases the clarity in organizing data.

Database Normalization (w3schools.in)


First Normal Form
• All the rows must be unique (no duplicate rows)
• Each cell must only contain a single value (not a list)
• Each value should be non divisible (cannot split down further)
Take away orders SOLUTION:
Fix the problem
by adding an
OrderID as
primary key

Two rows are


identical. That
is a problem.
First Normal Form
• All the rows must be unique (no duplicate rows)
• Each cell must only contain a single value (not a list / multiple list)
• Each value should be non divisible (cannot split down further)

Take away orders

Problem is there is multiple values in the Order Field.


SOLUTION: Create a new field in table with each
individual item.
First Normal Form
• All the rows must be unique (no duplicate rows)
• Each cell must only contain a single value (not a list)
• Each value should be non divisible (cannot split down further)
Problem is that it
must be atomic (non
divisible)

SOLUTION:
Create a column
for the First
Name and the
Last Name
Second Normal Form
• Database must be in First Normal Form (comply to the rules)
• Non partial dependency – All non prime attributes should be fully
functionally depended on the candidate key

Courses for Students


The Course Fee has nothing A composite key is derived from
to do with the Student ID a combination of two or more
without the Course ID. columns that combined make a
So Course Fee is not unique column, which individually
dependant on the Student ID does not provide uniqueness. 
which is part of the
Composite Key
Second Normal Form
• Database must be in First Normal Form (comply to the rules)
• Non partial dependency – All non prime attributes should be fully
functionally depended on the candidate key

Courses for Students

SOLUTION:
CREATE 2 DIFFERENT TABLES
AND DISPLAY INFORMATION
AS FOLLOWS
Third Normal Form
• Database must be in First & Second Normal Form
• No transitive dependency – All fields must only be determinable by the
primary/composite key, not by other keys

Tournament Winner Info

Problem: When I look at Winner I SOLUTION: CREATE ANOTHER


know when is his date of birth. It TABLE WITH TOURNAMENT
should not be determinable by WINNERS DATA AND THE
another field WINNERS DOB
Third Normal Form

The Winners DOB: the Date of Birth


Data in Tournament Winners Table is all corresponds with the Winners’
unique. The Winner is dependant on the information
Tournament and Year because each
tournament happens annually and you cannot
know who the winner is without the year or the
tournament information
1st, 2nd and 3rd Normal Form

1st Normal Form (1NF) 2nd Normal Form (2NF) 3rd Normal Form (3NF)

All the rows are unique and No Partial


No Transitive Dependencies
atomic Dependencies

1st, 2nd and 3rd Normal Form (Database Normalisation) - YouTube

You might also like