Employee Information

Employee Information

CPT 310 Database Systems and Management

Normalizing information is the process of efficiently organizing data in a database (Chapple, 2019). The goal of normalization is to get rid of information that is irrelevant data which could be data that is duplicated throughout the database. You also use normalization to make sure that database only has the information that is needed to be shown within the database. You want to make sure that you are using minimal storage space because when you don’t use this process, you can cause you system to lose vital information that was inside your database.

When normalizing the relational database, the table that is a relation is in 1NF. Each cell can only contain a single value. Every column must be different in the uniqueness of the name, but every entry must be the same kind. Also, no two rows can be the same. The table is two-dimensional with rows and columns. Each row contains data that pertains to some thing or portion of a thing. When you look at the columns, they represent a single attribute of the thing that is being described. Each column below has a unique name and no row is identical.

2NF focuses on the removal of duplicating data. As stated earlier in the discussion, the 2NF must meet the requirements of the 1NF. In order to remove duplicating data, the 2NF creates a separate table for the duplicated data. When a new employee is hired to a department, they are then added to the list but in a different table.

3NF will still have anomalies that have been created by problems with keys. Data that doesn't belong in the records will be removed from that table. Breaking the table into two tables solves the transitive dependency issue. The two tables below make up a database that is in the 3NF. Although most relational databases may not move past this normal form, it doesn't hinder the functionality of the database.