Scribd
Upload
27 views

Normalization in DBMS

The document discusses normalization, which is the process of organizing data in a database to minimize duplication and reduce data anomalies. It involves decomposing large relations into smaller, simpler relations by separating redundant attributes into new tables and linking them together with primary keys. Normalization results in relations that are in first normal form (1NF) through fifth normal form (5NF), with each higher normal form providing stronger data integrity. While normalization improves data consistency and flexibility, it can also degrade performance and increase the time required for database design.

Uploaded by

Aarushi Saxena
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
27 views

Normalization in DBMS

The document discusses normalization, which is the process of organizing data in a database to minimize duplication and reduce data anomalies. It involves decomposing large relations into smaller, simpler relations by separating redundant attributes into new tables and linking them together with primary keys. Normalization results in relations that are in first normal form (1NF) through fifth normal form (5NF), with each higher normal form providing stronger data integrity. While normalization improves data consistency and flexibility, it can also degrade performance and increase the time required for database design.

Uploaded by

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

Normalization

A large database defined as a single relation may result in data duplication. This
repetition of data may result in:

○ Making relations very large.

○ It isn't easy to maintain and update data as it would involve searching many
records in relation.

○ Wastage and poor utilization of disk space and resources.

○ The likelihood of errors and inconsistencies increases.

So to handle these problems, we should analyze and decompose the relations with
redundant data into smaller, simpler, and well-structured relations that are satisfy
desirable properties. Normalization is a process of decomposing the relations into
relations with fewer attributes.

What is Normalization?

○ Normalization is the process of organizing the data in the database.

○ Normalization is used to minimize the redundancy from a relation or set of


relations. It is also used to eliminate undesirable characteristics like Insertion,
Update, and Deletion Anomalies.

○ Normalization divides the larger table into smaller and links them using
relationships.

○ The normal form is used to reduce redundancy from the database table.

Why do we need Normalization?


The main reason for normalizing the relations is removing these anomalies. Failure
to eliminate anomalies leads to data redundancy and can cause data integrity and
other problems as the database grows. Normalization consists of a series of
guidelines that helps to guide you in creating a good database structure.
Data modification anomalies can be categorized into three types:

○ Insertion Anomaly: Insertion Anomaly refers to when one cannot insert a new
tuple into a relationship due to lack of data.

○ Deletion Anomaly: The delete anomaly refers to the situation where the
deletion of data results in the unintended loss of some other important data.

○ Updation Anomaly: The update anomaly is when an update of a single data


value requires multiple rows of data to be updated.

Types of Normal Forms:


Normalization works through a series of stages called Normal forms. The normal
forms apply to individual relations. The relation is said to be in particular normal
form if it satisfies constraints.

Following are the various types of Normal forms:


Normal Description
Form

1NF A relation is in 1NF if it contains an atomic value.

2NF A relation will be in 2NF if it is in 1NF and all non-key attributes are fully

functional dependent on the primary key.

3NF A relation will be in 3NF if it is in 2NF and no transition dependency

exists.

BCNF A stronger definition of 3NF is known as Boyce Codd's normal form.

4NF A relation will be in 4NF if it is in Boyce Codd's normal form and has no

multivalued dependency.

5NF A relation is in 5NF. If it is in 4NF and does not contain any join

dependency, joining should be lossless.

Advantages of Normalization

○ Normalization helps to minimize data redundancy.

○ Greater overall database organization.

○ Data consistency within the database.

○ Much more flexible database design.

○ Enforces the concept of relational integrity.


Disadvantages of Normalization

○ You cannot start building the database before knowing what the user needs.

○ The performance degrades when normalizing the relations to higher normal


forms, i.e., 4NF, 5NF.

○ It is very time-consuming and difficult to normalize relations of a higher


degree.

○ Careless decomposition may lead to a bad database design, leading to


serious problems.

You might also like