Database Normalization: Detailed Explanation of 1NF and 2NF Forms

The assignment solution provides a detailed explanation of database normalization, specifically focusing on First Normal Form (1NF) and Second Normal Form (2NF). It demonstrates the process of transforming two tables, a Customer Table and an Events Table, into 1NF and 2NF respectively. For the Customer Table, the solution involves creating separate Customer and Contact tables to eliminate repeating groups, establishing a relationship between them using CustomerID as a primary and foreign key. Similarly, for the Events Table, a Course table is created to avoid repetition of course information, with CourseID serving as the linking key. The solution emphasizes that both resulting sets of tables adhere to the rules of 1NF and 2NF, ensuring that each table has a primary key and all other fields are dependent on that key, thus achieving a normalized database structure. The document references external sources to support the explanations.

Database Normalization
March 12
201
9
Student ID:
Student Name:
Module Tutor:
Module:

Customer Table in First Normal Form (1 NF)
Customer Table
CustomerID Name City
1 ACME Corp Denver
2 Two Trees Ojai
3 Acacia Edinburgh
Contact Table
CustomerID ContactName
1 Maria Donald
2 Helen Bale
3 Martin Brown
3 Karen Dick
3 Jack Watkins
Following steps are used to make the customer table into first normal form-
- Generate a new table customer.
- Generate a new table contact because there is more than one contact for a customer.
- Make a relationship in between the customer and contact table.
Both tables are following the rules of first normal form because there is no repeated group in
both tables. Each table has primary key and all other fields are depending upon the primary key
only.
The CustomerID is the primary key in the Customer table and working as a foreign key in the
Contact table. A customer may have more than one contact therefore; the cardinality is 0..1 to
0..* from Customer table to Contact table.

Events table in Second Normal Form (2 NF)
Course Table
Course CourseTitle
SQL101 Intro to SQL
DB101 Database Design
Event Table
EventID CourseID Date Seats Room
1 SQL101 4/2/10 5 14
2 SQL101 5/4/10 2 11
3 SQL101 6/9/10 4 8
4 DB101 5/4/10 6 11
Following steps are used to make the Events table into second normal form-
- Generate a new table Course as same course and titles are being repeated into the Events
table.
- Generate a new table Event.
- Make a relationship in between the Course and Event table.
Both tables are following the rules of second normal form as in both tables there is no repeated
group. Each table has primary key and all other fields are depending upon the primary key only.
The CourseID is the primary key in the Course table and working as a foreign key in the Event
table. A course may be involved in more than one event therefore; the cardinality is 0..1 to 0..*
from Course table to Event table.

(Peter Brombarg. n.d.)
(1keydata.com. 2015)
References
Peter Brombarg. (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
1keydata.com. (2015). Database Normalization. Retrieved from
http://www.1keydata.com/database-normalization/