Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
6 views4 pages

Normalization DBMS

Normalization in DBMS is a process that organizes data to minimize redundancy and enhance data integrity by decomposing tables and defining relationships. It includes several normal forms (1NF, 2NF, 3NF, BCNF) that establish specific requirements to eliminate data anomalies and improve query efficiency. Each normal form addresses different types of data dependencies, ensuring a structured and efficient database design.

Uploaded by

Atharva Wadhavane
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
6 views4 pages

Normalization DBMS

Normalization in DBMS is a process that organizes data to minimize redundancy and enhance data integrity by decomposing tables and defining relationships. It includes several normal forms (1NF, 2NF, 3NF, BCNF) that establish specific requirements to eliminate data anomalies and improve query efficiency. Each normal form addresses different types of data dependencies, ensuring a structured and efficient database design.

Uploaded by

Atharva Wadhavane
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

Database Normalization

Normalization in DBMS

Normalization is a process in relational database design that organizes data to reduce redundancy and

improve data integrity.

It involves decomposing a table into smaller tables and defining relationships between them.

Why Normalization is Needed:

1. Avoid Data Redundancy

2. Ensure Data Consistency

3. Improve Data Integrity

4. Make Queries Efficient

5. Prevent Anomalies

Normal Forms:

1NF (First Normal Form)

- Atomic values (no repeating groups or arrays)

- Each cell must contain a single value

Example (Not in 1NF):

| StudentID | Name | Courses |

|-----------|-------|-----------------|

|1 | Alice | Math, Physics |

|2 | Bob | Chemistry |

1NF:

| StudentID | Name | Course |

|-----------|-------|------------|

|1 | Alice | Math |

|1 | Alice | Physics |
Database Normalization

|2 | Bob | Chemistry |

2NF (Second Normal Form)

- Must be in 1NF

- No partial dependency

Example (Not in 2NF):

| StudentID | Course | InstructorName |

|-----------|----------|----------------|

|1 | Math | Mr. A |

|1 | Physics | Mr. B |

2NF (Decomposed):

Table 1: Student_Courses

| StudentID | Course |

|-----------|--------|

|1 | Math |

|1 | Physics|

Table 2: Course_Instructors

| Course | InstructorName |

|----------|----------------|

| Math | Mr. A |

| Physics | Mr. B |

3NF (Third Normal Form)

- Must be in 2NF

- No transitive dependency

Example (Not in 3NF):


Database Normalization

| StudentID | Name | Department | HOD |

|-----------|--------|------------|------------|

|1 | Alice | Science | Dr. Smith |

|2 | Bob | Arts | Dr. Allen |

3NF:

Table 1: Students

| StudentID | Name | Department |

|-----------|--------|------------|

|1 | Alice | Science |

|2 | Bob | Arts |

Table 2: Departments

| Department | HOD |

|------------|------------|

| Science | Dr. Smith |

| Arts | Dr. Allen |

BCNF (Boyce-Codd Normal Form)

- Stricter version of 3NF

- Every determinant must be a candidate key

Example (Not in BCNF):

| StudentID | Course | Instructor |

|-----------|--------|------------|

|1 | Math | Mr. A |

|2 | Math | Mr. A |

BCNF:

Table 1: Course_Instructors
Database Normalization

| Course | Instructor |

|--------|------------|

| Math | Mr. A |

Table 2: Student_Courses

| StudentID | Course |

|-----------|--------|

|1 | Math |

|2 | Math |

Summary:

| Normal Form | Requirement | Removes |

|-------------|-------------------------------------|-------------------------|

| 1NF | Atomic values | Repeating groups |

| 2NF | No partial dependency | Partial dependencies |

| 3NF | No transitive dependency | Transitive dependencies |

| BCNF | Determinant must be a candidate key | Any dependency issues |

You might also like