0% found this document useful (0 votes)
26 views

Normalization of Relations

The document discusses normalization of relations in a database. Normalization is the process of organizing data to reduce redundancy and anomalies like insertion, update, and deletion anomalies. It involves dividing larger tables into smaller tables and linking them using relationships. The document discusses first normal form, which requires that attributes are single-valued, and second normal form, which requires that tables are in 1NF and have no partial dependencies.

Uploaded by

Deshna Jain
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views

Normalization of Relations

The document discusses normalization of relations in a database. Normalization is the process of organizing data to reduce redundancy and anomalies like insertion, update, and deletion anomalies. It involves dividing larger tables into smaller tables and linking them using relationships. The document discusses first normal form, which requires that attributes are single-valued, and second normal form, which requires that tables are in 1NF and have no partial dependencies.

Uploaded by

Deshna Jain
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

DBMS (Prof.

Neil Joshi)

Normalization of Relation
• NORMALIZATION is the process of organizing the data in the
database.
• It is used to reduce Redundancy from relation or set of relation.
• It is also used to eliminate undesirable characteristics like
Insertion, Update, and Deletion anomalies.
• It divides the larger table in the smaller and links them using the
relationship.
• The Normal form is used to reduce redundancy from the
database table.
DBMS (Prof. Neil Joshi)

Normalization of Relation
Why Normalization of Relation is required?
DBMS (Prof. Neil Joshi)

Normalization of Relation
Data Modification Anomalies and their Categorization:
DBMS (Prof. Neil Joshi)

Normal Forms
1N Form: (First Normal Form)
DBMS (Prof. Neil Joshi)

Normal Forms
1N Form: (First Normal Form)
• If a relation contains composite or Multi-valued Attribute, then
it violates First Normal Form.

• If a relation is said to be in First Normal Form if Every Attribute


in that relation is single valued Attribute.
DBMS (Prof. Neil Joshi)
Normal Forms
1N Form: (First Normal Form)
Example-1: Consider a Table

This Table is not in 1st Normal Form


Converting the Table in 1st Normal Form
DBMS (Prof. Neil Joshi)
Normal Forms
1N Form: (First Normal Form)
Example-2: Consider a Table Converting the Table in 1st Normal Form

This Table is not in 1st Normal Form


DBMS (Prof. Neil Joshi)

Normal Forms
2N Form: (Second Normal Form)
DBMS (Prof. Neil Joshi)

Normal Forms
2N Form: (Second Normal Form)
• To be in 2nd Normal Form, the relation must be in 1st Normal
Form and
• The relation must not contain any partial dependency.
• Therefore a relation in 2N Form has No Partial Dependency.
• i.e. no Non-Prime attribute (attributes which are not part of any
candidate key) is dependent on any proper subset of any
candidate key of the table.
• Partial Dependency: If the proper subset of candidate key determines
non-prime attribute
DBMS (Prof. Neil Joshi)
Normal Forms
2N Form: (Second Normal Form)
Example-1: Consider a Table • There are many courses having the
same course fee.

• COURSE_FEE cannot alone decide the


value of COURSE_NO or STUD_NO;
• COURSE_FEE together with STUD_NO
cannot decide the value of
COURSE_NO;
• COURSE_FEE together with
COURSE_NO cannot decide the value
of STUD_NO;
DBMS (Prof. Neil Joshi)
Normal Forms
2N Form: (Second Normal Form)
Example-1: Consider a Table • Hence, COURSE_FEE would be a non-prime
attribute, as it does not belong to the one
only candidate key {STUD_NO, COURSE_NO}

• But, COURSE_NO -> COURSE_FEE, i.e.,


COURSE_FEE is dependent on COURSE_NO,
which is a proper subset of the candidate key

• Non-prime attribute COURSE_FEE is


dependent on a proper subset of the
candidate key, which is a partial dependency
and so this relation is not in 2NF.

Hence This Table is not in 2nd Normal Form

You might also like