Normalization in Database

Management Systems

ANUBHAB BARIK.(22/IT/037)
AYAN SAMANTA.(22/IT/057)
ARCHISMAN DUTTA.(22/IT/042)
DHIMAN BERA.(22/IT/070)
ANUP SAMANTA.(22/IT/039)
Introduction to
Normalization
Eliminating Enhancing Data Improving Data
Redundancy Integrity Efficiency
Normalization helps reduce data By eliminating redundancy, Normalized databases are more
redundancy by storing each piece normalization ensures that data is efficient to access and update, as
of information only once, consistent and accurate, data is organized in a structured
minimizing storage space and preventing data anomalies and and logical manner.
potential inconsistencies. ensuring reliable information.
Importance of
Normalization
1 1. Data Consistency 2 2. Reduced Data 3 3. Improved Query
Ensures that changes to data Duplication Performance
are reflected consistently Minimizes storage space and Normalized databases are
across the database, reduces the risk of data optimized for efficient data
preventing inconsistencies. inconsistencies arising from retrieval, leading to faster
redundant data. query execution.
First Normal Form
(1NF)
Atomic Values No Repeating Example
Ensures that each cell in a table Groups repeating groups of
Eliminates Consider a table with multiple
contains only one atomic value, data by separating them into phone numbers in a single cell.
meaning a single piece of distinct tables, with relationships 1NF would separate these into
information. maintained through foreign keys. distinct rows with individual
phone numbers.
Second Normal Form
(2NF)
Eliminate Partial Example
Dependencies
Ensures that non-key attributes are fully dependent on A table storing customer details might have a partial
the primary key, eliminating partial dependencies. dependency if 'address' depends on 'city', which in turn
depends on the customer's 'ID'. 2NF would separate
address and city into a separate table.
Third Normal Form
(3NF) Transitive Dependency
1
Removal
Eliminates transitive dependencies, where non-key attributes are dependent on other non-key
attributes.

Example
2
A table storing 'employee' data with 'department ID' and 'department location' exhibits transitive
dependency. 3NF would separate 'department' details into a separate table.
Boyce-Codd Normal Form
(BCNF)
Stricter Than 3NF
BCNF is a stricter form than 3NF, requiring that every determinant be a candidate key.

Minimizes Data
Redundancy
BCNF reduces redundancy further by eliminating any potential functional dependencies between non-
key attributes.

Example
A table storing 'project' data with 'project ID' and 'team members' may exhibit functional dependencies
between non-key attributes in 3NF, but not in BCNF.
Fourth Normal Form
(4NF)
Multivalued Dependency
Removal
4NF addresses multivalued dependencies, where an attribute can
1 have multiple values independent of other attributes.

Example
A table storing 'student' data with 'courses' and
2
'hobbies' exhibits multivalued dependency. 4NF would
separate these into separate tables.
Fifth Normal Form
(5NF)
Join Dependency
1 Elimination
5NF addresses join dependencies, where data can be decomposed into multiple tables and
joined back together to reconstruct the original data.

Highly Specialized
2 5NF is a highly specialized form that is rarely encountered in practical
database design.

Example
A table storing 'supplier' data with 'parts' and
3
'projects' might exhibit join dependency. 5NF would
further decompose these into separate tables.
Applying Normalization
Principles
1 2
Analyze Data Identify Keys
Understand the relationships and dependencies within Determine primary keys and candidate keys for each
your data. table.

3 4
Apply Normal Forms Validate Design
Decompose tables to eliminate redundancy and achieve Test your design to ensure data integrity and query
the desired normal form. performance.