Normalization… Why?{1}

by Evin C
Normalizing data has become an important aspect of our course which is why I chose this article. Looking through the full article not only gives you a perspective on normalizing data but also unique ways to approach it. Having already gone over the ways to normalize data in class, this summarizes that information yet again to hopefully appeal to more people and help everyone better understand the process. Although it does not have labeled examples, it does have in depth details about each individual normal form and how they are converted and applied. The article then goes on to evaluate how accuracy and performance affect a database, saying “a poorly normalized database and poorly normalized tables can cause problems ranging from excessive disk I/O and subsequent poor system performance to inaccurate data.” It even goes on to say “an improperly normalized condition can result in extensive data redundancy, which puts a burden on all programs that modify the data.”

These examples given relate directly to class through our discussion about how data is affected by normalization and what can be the pitfalls of it. Now, if normalizing is done correctly then it can provide a tremendous amount of help but if done incorrectly it can lead to some disastrous results. Using these methods in any type of organization comes with a major responsibility to use their data correctly and efficiently.

Throughout the next few weeks I hope to learn more about data normalization and it’s application to the real world. Having these projects is only going to further our knowledge and hopefully give us some perspective on how we can even apply it to our lives today. For those of you who have read my blog, I definitely recommend at least a brief look at this article.


Poolet, M. A. (1999, March 01). Sql by design: Why you need database normalization. Retrieved from