0% found this document useful (0 votes)
3 views

4 Database Design

The document outlines the principles of database design, focusing on functional dependencies and the normalization process. It details the various normal forms (1NF to 5NF) that aim to reduce redundancy and dependency in database structures. Each normal form builds upon the previous one, ensuring data integrity and efficient organization.

Uploaded by

jallumanikanta07
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views

4 Database Design

The document outlines the principles of database design, focusing on functional dependencies and the normalization process. It details the various normal forms (1NF to 5NF) that aim to reduce redundancy and dependency in database structures. Each normal form builds upon the previous one, ensuring data integrity and efficient organization.

Uploaded by

jallumanikanta07
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Database Design

1. Functional Dependencies
A functional dependency is a constraint between two sets of
attributes in a relation (table). It describes a relationship
where one attribute uniquely determines another attribute. If
we say A -> B, it means that if two rows in a table have the
same value for A, they must have the same value for B .
Here, A is called the determinant of B .
Key Points:
• Functional dependencies are crucial in identifying
redundancy.
• They guide the normalization process by indicating
which attributes depend on others.

2. Process of Normalization
Normalization is a step-by-step process of refining the
structure of a database by organizing data to reduce
redundancy and dependency. It involves dividing large tables
into smaller tables and defining relationships between them.
The main goal of normalization is to ensure that each piece of
data is stored only once.
The normalization process includes various normal forms
(NFs), each adding a level of rigor to the database design.

3. First Normal Form (1NF)


A table is in First Normal Form (1NF) if it meets the following
conditions:
• Atomicity: Each cell in a table must contain only one
value (no multiple values).
• No repeating groups: There should be no arrays or lists
within cells; each piece of information should be stored
separately.
1NF is the foundational level of normalization, establishing
that each attribute contains indivisible values.

4. Second Normal Form (2NF)


A table is in Second Normal Form (2NF) if it:
1. Is already in 1NF.
2. Has no partial dependencies (where a non-key attribute
depends on only a part of a composite primary key).
To achieve 2NF, we remove any partial dependencies by
splitting tables and linking them with primary keys.
5. Third Normal Form (3NF)
A table is in Third Normal Form (3NF) if it:
1. Is in 2NF.
2. Has no transitive dependencies (where a non-key
attribute depends on another non-key attribute).
In other words, 3NF ensures that all attributes are dependent
only on the primary key and nothing else.
6. Boyce-Codd Normal Form (BCNF)
Boyce-Codd Normal Form (BCNF) is a higher version of 3NF,
with the additional requirement:
• Every determinant must be a candidate key.
BCNF addresses certain edge cases not covered by 3NF, often
involving tables with multiple overlapping candidate keys.
7. Fourth Normal Form (4NF)
A table is in Fourth Normal Form (4NF) if it:
1. Is in BCNF.
2. Has no multi-valued dependencies (when one attribute
in a table uniquely determines another attribute,
independently of other attributes).
4NF is necessary when dealing with complex relationships
where one attribute can determine multiple independent
attributes.

8. Fifth Normal Form (5NF)


A table is in Fifth Normal Form (5NF) if it:
1. Is in 4NF.
2. Has no join dependencies (situations where certain
combinations of data can be reconstructed only by
joining multiple tables).
5NF is the highest level of normalization, addressing cases
where complex relationships exist, and data can be broken
down further without losing information.

You might also like