A
SEMINAR PRESENTATION
ON
CONCEPT OF NORMALIZATION
(WITH RESPECT TO SECOND NORMAL FORM 2NF)
BY
(GROUP E MEMBERS)
ESSIEN, DANIEL ITA
@
DEPARTMENT OF COMPUTER SCIENCE
AKWA IBOM STATE UNIVERSITY, IKOT AKPADEN MKPAT ENIN
(MAIN CAMPUS)
NOVEMBER, 2016
INTRODUCTION
Designing a relational database to minimize data redundancy (and
therefore maximize data integrity) is called normalization.
It can be considered as a filtering or purification process to make the
design have successively better quality. Unsatisfactory relation schemas
that do not meet certain conditions - the normal form tests - are
decomposed into smaller relation schemas that meet the tests and hence
possess the desirable properties.
The normal form of a relation refers to the highest normal form
condition that it meets, and hence indicates the degree to which it has
been normalized.
All these normal forms are based on a single analytical tool: the
functional dependencies among the attributes of a relation.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 2
WHY DO WE NORMALIZE?
Save typing of repetitive data.
Increase flexibility to query, sort, summarize, and
group data (Simpler to manipulate data!).
Avoid frequent restructuring of tables and other
objects to accommodate new data.
Reduce disk space .
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 3
FUNCTIONAL DEPENDENCY
A functional dependency (FD) exists between two fields, A and B, when a
distinct value of A is directly associated with a distinct value of B.
Functional Dependency is diagrammed as AB.
An excellent example of a functional dependency is a Primary Key. The
Primary Key functionally determines all non-key fields in the table given
a Primary Key value for a specific record in a table, you can retrieve the
values of the remaining non-key fields in that record.
Customer Table showing functional dependency.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 4
FIRST NORMAL FORM (1NF)
First Normal Form (1NF) defines the rule that all the attributes
in a relation must have atomic domains.
It states that the domain of an attribute must include only
atomic (simple, indivisible) values and that the value of any
attribute in a tuple must be a single value from the domain of
that attribute.
It is defined to disallow multi-value attributes, composite
attributes, and their combinations.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 5
FIRST NORMAL FORM (1NF)
These are the conditions that satisfy the First Normal Form Test;
Is each column an attribute of the table's entity?
Is there a primary key?
Are there no duplicate rows?
Are there no repeating columns?
Are there no multiple values in any column of any row?
Consider the warehouse table below: This violates the First
Normal Form.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 6
FIRST NORMAL FORM (1NF)
Warehouse table conforming to the First Normal Form (1NF):
LIMITATION OF FIRST NORMAL FORM
It does not support multi-valued attributes and composite
values thereby making it inefficient.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 7
SECOND NORMAL FORM
A relation is in second normal form (2NF) if it is in first
normal form and contains no partial functional
dependencies.
A partial functional dependency exists when a non-key
attribute is functionally dependent on part (but not all) of
the primary key.
Its usually used in tables with a multiple-field primary key
(composite key).
One of the composite keys is arbitrarily designated to be the
primary key, and the others are called secondary keys.
Second normal form eliminates data redundancy.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 8
SECOND NORMAL FORM
The tests that should be applied to check 2NF on every table in
the database are;
Is each criteria of 1NF satisfied?
What are the composite keys? For each composite key, what
columns are not parts of the composite key? Is each such
column dependent on the entire composite key?
TABLE VIOLATING TO SECOND NORMAL FORM
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 9
SECOND NORMAL FORM
TABLES CONFORMING TO SECOND NORMAL FORM (2NF)
NOTE: First Normal Form deals with atomicity of data, the Second Normal
Form (or 2NF) deals with relationships between composite key columns and
non-key columns.
LIMITATION OF SECOND NORMAL FORM
It contains a transitive dependency.
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 10
CONCLUSION
We have seen how Database Normalization can
decrease redundancy in 1NF and increase
efficiency and reduce anomalies in 2NF and
their limitations. The first three NFs are
usually sufficient for most small to medium
size applications.
THANK YOU FOR LISTENING
2/22/17 NORMALIZATION WITH RESPECT TO SECOND NORMAL FORM(2NF) 11
