Database Normalization Explained

This assignment delves into the concept of database normalization, explaining its importance and various normal forms (1NF, 2NF, and 3NF). It provides a dependency diagram illustrating relationships between different entities and attributes, highlighting how normalization ensures data integrity and reduces redundancy. The assignment also explores relational schemas and presents an ER diagram for a practical understanding of normalization principles.

Normalisation
Student ID –
Student Name –
Subject Code -
Date -

Report
Dependency Diagram
Product Name, Product Price, Vendor ID and Vendor Name depends upon the
ProductCode.
ProductName  ProductCode
ProductPrice  ProductCode
VendorID  ProductCode
VendorName  ProductCode
Purchase Date and Invoice Date depends upon the InvoiceNumber.
PurchaseDate  InvoiceNumber
InvDate  InvoiceNumber
Vendor Name depends upon the Vendor ID.
VendorName  VendorID
Sold Quantity depends upon the Pruduct Code and Invoice Number.
QuantitySold  ProductCode
QuantitySold  InvoiceNumber
(Brombarg P. n.d.)

3NF Relations
1 NF
2 NF

3 NF
Third normal is achieved by following rules-
- All entities are having unique key for identification.
- Other fields depend upon that unique key only.
- Transitive dependency is not involved in any entity.

Relational Schema
(Guru99 2016)

ER Diagram
References
Guru99 (2016), Learn Database Normalization with the help of a case study,
Retrieved from
http://www.guru99.com/database-normalization.html
Brombarg P. (n.d.) SQL SERVER Database Normalization Basics for Developers,
Retrieved from
http://www.nullskull.com/a/1629/sql-server-database-normalization-basics-for-
developers.aspx