Database Normalization

DATABASE NORMALIZATION

Daltrin Wardell

DBM 380

October 9, 2011

ABSRACT

In the following paper I plan to discuss how database normalization can divide incoming data into smaller yet more manageable data tables for a company named Huffman Trucking. Normalization of the database is most often seen as the most effective method to either drastically reduce or completely eliminate data redundancies. Database normalization also helps the designer ensure that tables are related in the correct form and result in the reduction of possible anomalies. Many companies whom require a database system to be set up are reluctant to give a database designer the proper time or financial support to normalize a database, but cases have shown that without this process database generally are slower to produce query results and may contain inaccuracies that could have otherwise been avoided. According to an article by author David Adams some of the standard benefits of database normalization include, "a more efficient database structure, better understanding of your data, a more flexible database structure, avoiding redundant fields, and ensuring that distinct tables exist when necessary." (Programming 4th Dimension)

NORMALIZATION DESCRIPTION

In an effort to avoid redundancy the repetitive groups inside the Huffman Driving log will be relocated to a separate table. The groups OffDutyStartTime1, OffDutyStartTime1, OffDutyStopTime 2, OffDutyStopTime 2, will be moved into a new table labeled "TimeTable". The TimeTable table will include StartTime, StopTime, and the TypeOfTimeID. The TypeOfTimeID is recognized as the foreign key and can be referenced in another table. The table will look as follows:

Time_Type_ID

UniqueIdentifer

Time_Type_Name Varchar Could be OffDuty, OnDuty, Driving, Odometer, etc.

The Co-drivers name has been taken off the "Driving Log" table because you can find the drivers details from the Co_Driver_EmpID data. In the proceeding "Violations" table the State/Municipality_Issuing_Citation is deleted and StateID will be included. The "State" table will house the StateID, or the State/Municipality_Issuing_Citation group and should look as follows:

StateID

UniqueIdentifer

Examples - TX,OH, NY, etc.

State/Municipality_Issuing_Citation Varchar Could