Database Normalization

Database Normalization

1. Database normalization is a very important process in designing and organizing tables (relations) and their columns (attributes or fields) in a relational database. Therefore, what are the consequences (problems) if a database was designed without it? Would the database still work?

Database normalization is defined as “the process of reorganizing data in a database so that it meets two basic requirements: (1) There is no redundancy of data (all data is stored in only one place), and (2) data dependencies are logical (all related data items are stored together).”

Since the goal of database normalization is to ensure no redundancy in data and to make sure that related data items are stored in a logical format, database normalization can help speed things up and make sure that the data is reliable. However, this does not mean that database normalization is applicable to all situations. As with any design, there are reasons why database normalization could prove to be ineffective and not the best practice. For a small company, database normalization can prove to be expensive. The practice often involves a lot of tables and table joins can be extensive. In the instance of multi-join queries, database normalization could work against the process. Secondly, database normalization can be difficult. If there is a complex scheme in place, database normalization can be hard to work with. Lastly, in creating prototypes and/or needing rapid development, database normalization isn’t necessary. A lot of time can be spent on normalization just to discover that the prototype needs to be scrapped and recreated. (Chapple, 2014)

In the end, databases will work without normalization. Database normalization has progressed to being a best practice but as with any design, the need for it should be determined by environmental factors such as size, budget, need, etc.

What is Normalization? – Definition from Techopedia. (n.d.). Retrieved November 05, 2016, from https://www.techopedia.com/definition/1221/normalization

Chapple, M. (2014). Should I Normalize My Database? Retrieved November 05, 2016, from http://databases.about.com/od/specificproducts/a/Should-I-Normalize-My-Database.htm