was broken up into 11 tables. The database is in the third normal form or Boyce Codd Normal Form (BCNF) (Pratt & Adamski, 2005, p. 153). This level of normalization ensures no repeating groups, no key column is dependent on only a portion of the primary key, and the only determinants that are contained are candidate keys. The company has four locations in the United States and services 925 drivers. Normalization to the third normal form is sufficient due to the relatively small database, the number
six generally recognized normal forms of a relation: first normal form, second normal form, third normal form, Boyce/Codd normal form, fourth normal form, and fifth normal form, also called projection/join normal form. Other normal forms (e.g., Domain/Key) exist but will not be discussed here. The normal forms are hierarchical, i.e., each normal form builds upon its predecessor. Although many people consider a relation to be normalized only when it is in third normal form, technically speaking, a
it still using navigational system and complex in implementation. And the change in structure requires a changes in all application program (Morris 55). The major evolution of data model happen in 1970 when “relational model was introduced by E.F. Codd of IMB in his landmark paper “A relational Model
Inconsistently storing organization data creates a lot of issues, a poor database design can cause security, integrity and normalization related issues. Majority of these issues are due to redundancy and weak data integrity and irregular storage, it is an ongoing challenge for every organization and it is important for organization and DBA to build logical, conceptual and efficient design for database. In today’s complex database systems Normalization, Data Integrity and security plays a key role