Database or data normalization is often an overlooked aspect of database design. Essentially, normalizing data involves the process of efficiently organizing data and table structures in a database. This process is especially important in large databases that experience a high volume of updates or changes daily. Without database normalization, databases can quickly become difficult to maintain and experience sluggish or inefficient performance. This document will attempt to describe and list the benefits of database normalization.
What is Database Normalization.
Database normalization involves the practice of optimizing data and tables in a database. The primary goals of database normalization are:.
Arranging data into logical groupings such that each group describes a small part of the whole; minimizing the amount of duplicate data stored in a database; organizing data such that, when you modify it, you make the change in only one place; and building a database in which you can access and manipulate the data quickly and efficiently without compromising the integrity of the data in storage (Poolet, 1999, par. 4).
In order to ensure proper data normalization, thorough analysis of the data being stored in the database should first be conducted. In addition, relationships between the data should also be considered.
Generally, there are three normal form rules that one must follow when normalizing data. The first normal form (1NF), also the most basic, involves the initial removal of repeating groups of data within a table. Separate tables should be created for each group of related data. The second normal form (2NF) requires the elimination of redundant or duplicate data. Finally, the third normal form (3NF) calls for the purging of all columns or attributes that are not directly dependant upon the primary key. These three normal forms are usually enough to ensure efficient database normalization (Gilmore, 2000).
