Normalization Made Easy{1}



The article I read teaches the basics of normalizing data.  In this class we recently learned the benefits of normalizing data.  If data exists in one more then location in a database, then one should have the ability to change data in one location on the database, and then have that change applied to rest of its similar entries in the database.  That is why having a strong link between redundant entries and formal rules of structure in a database are so important.  For data to be considered normalized, it must reach the third level of normalization.  The first form of normalization requires that a database eliminate repeating groups, create separate tables for each set of related data, and identify each set of related data with a primary key.  One would think this set of requirements is expected of any professional database.  The second form requires that a separate table is created for values applied to multiple records, and that these tables are related due to a foreign key.  The third form requires that one eliminates any field not dependent on a key.

I chose this article because it helped explain the normalization process in an easy and clear way.  This is something we covered the last few times we’ve been in class and remains an important issue.  The article URL is posted below and I recommend it for anyone struggling with this subject.

In conclusion, it is important that we all grasp this topic as it will become very important once we begin designing our own databases.  I have taken database classes in the past and can tell you from experience that it is very easy to create a database for an assignment that seems to be well-made, until you try to apply the third form of normalization and realize that many design flaws exist in your database.

Citation

Microsoft. (2007, January 29). Description of database normalization basics. Retrieved on January 29, 2011 from http://support.microsoft.com/kb/283878