Scribd
Upload
2 views9 pages

Database: What Is Normalization? It Is A Technique To Reduce Redundancy From The Table

Normalization is a database design technique aimed at reducing redundancy and organizing data efficiently. It involves several normal forms (1NF to 5NF) that establish specific criteria for structuring tables to eliminate issues like duplicate rows, partial dependencies, and transitive dependencies. Each normal form builds on the previous one, ensuring data integrity and minimal redundancy through systematic decomposition of tables.

Uploaded by

aysarnobat.zpk.rnt
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
2 views9 pages

Database: What Is Normalization? It Is A Technique To Reduce Redundancy From The Table

Normalization is a database design technique aimed at reducing redundancy and organizing data efficiently. It involves several normal forms (1NF to 5NF) that establish specific criteria for structuring tables to eliminate issues like duplicate rows, partial dependencies, and transitive dependencies. Each normal form builds on the previous one, ensuring data integrity and minimal redundancy through systematic decomposition of tables.

Uploaded by

aysarnobat.zpk.rnt
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/ 9

Database

Friday, January 3, 2025 9:21 AM

What is normalization?
It is a technique to reduce redundancy from the table.

Normalizati Definition Key Requirements Purpose Example


on Form
1NF A relation is in 1NF if it has only atomic - Each column has atomic values.- Rows Eliminates duplicate rows and A table storing customer data where each cell contains
(indivisible) values and each column contains are uniquely identifiable (with a primary ensures data is organized in a single value (e.g., one phone number per customer).
unique values for that attribute. key). tabular format.
2NF A relation is in 2NF if it is in 1NF and all non-prime - Must be in 1NF.- Non-prime attributes Removes partial dependency. Splitting a table into two to ensure that attributes
attributes are fully functionally dependent on the must depend on the entire primary key related to only part of a composite key are stored in a
entire primary key. (eliminates partial dependency). separate table.
3NF A relation is in 3NF if it is in 2NF and there are no - Must be in 2NF.- No transitive Removes transitive Creating a separate table for department names if they
transitive dependencies (non-prime attributes dependency (no non-prime attribute dependency. indirectly determine an employee’s address via a
depend only on the primary key). depends on another non-prime attribute). department ID.
BCNF A stricter version of 3NF where every determinant - Must be in 3NF.- Every determinant must Ensures minimal redundancy A table that contains attributes for professors and
(Boyce- is a candidate key. be a candidate key (eliminates and dependency. courses split into two to prevent a non-candidate key
Codd) dependency anomalies). determining another attribute.
4NF A relation is in 4NF if it is in BCNF and has no - Must be in BCNF.- No multi-valued Removes multi-valued Splitting a table with attributes for students and
multi-valued dependencies (MVDs). dependencies (MVDs). dependency. hobbies into separate tables, one for hobbies and
another for skills, to eliminate MVDs.
5NF A relation is in 5NF if it is in 4NF and cannot be - Must be in 4NF.- No join dependency Prevents loss of data during Decomposing a table to separate supplier, part, and
further decomposed into smaller tables without (JD). recombination. project relationships into individual tables to preserve
losing data (removes join dependency). information during recombination operations.

New Section 1 Page 1

You might also like