Scribd
Upload
9 views5 pages

Database Normalization

Database normalization is a method to organize databases by reducing redundancy and enhancing data integrity through the division of large tables into smaller ones. The first three normal forms are First Normal Form (1NF), Second Normal Form (2NF), and Third Normal Form (3NF), each with specific criteria for structuring tables. 1NF ensures atomic values, 2NF eliminates partial dependencies, and 3NF removes transitive dependencies among non-key attributes.

Uploaded by

Blessing
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
9 views5 pages

Database Normalization

Database normalization is a method to organize databases by reducing redundancy and enhancing data integrity through the division of large tables into smaller ones. The first three normal forms are First Normal Form (1NF), Second Normal Form (2NF), and Third Normal Form (3NF), each with specific criteria for structuring tables. 1NF ensures atomic values, 2NF eliminates partial dependencies, and 3NF removes transitive dependencies among non-key attributes.

Uploaded by

Blessing
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/ 5

DATABASE NORMALIZATION

TABLES

CHIBI TINODAISHE M
0781081816
Database normalization is a process used to organize a database in order to reduce redundancy
and improve data integrity. It involves dividing large tables into smaller ones and defining
relationships between them. There are several normal forms, with the first three being the most
commonly discussed: First Normal Form (1NF), Second Normal Form (2NF), and Third Normal
Form (3NF).

First Normal Form (1NF)

Definition: A table is in 1NF if:

1. All columns contain atomic (indivisible) values.

2. Each column contains values of a single type.

3. Each column must have a unique name.

4. The order in which data is stored does not matter.

Example:

Consider a table storing student information:

This table is not in 1NF because the Courses column contains multiple values. To convert it to 1NF,
we separate the courses into individual rows:
Second Normal Form (2NF)

Definition: A table is in 2NF if:

1. It is already in 1NF.

2. All non-key attributes are fully functionally dependent on the primary key.

Example:

Using the previous example, let's say we also want to store the student's major:

Here, the Major is dependent on StudentID, but the table is still in 2NF because Course is not
dependent on Name or Major alone.

To convert it to 2NF, we need to remove partial dependencies. We create two tables:

Students Table:
Courses Table:

Third Normal Form (3NF)

Definition: A table is in 3NF if:

1. It is already in 2NF.

2. There are no transitive dependencies (non-key attributes should not depend on other non-
key attributes).

Example:

Using the Students table from 2NF, suppose we also want to store the department information:

Students Table:
Majors Table:

Summary

• 1NF: Ensures atomicity of values in each column.

• 2NF: Eliminates partial dependencies; all non-key attributes depend on the entire primary
key.

• 3NF: Eliminates transitive dependencies; non-key attributes should not depend on other
non-key attributes.

You might also like