Database Design Mistakes{3}


A poorly designed database can lead to many problems down the road. It may not be apparent at first, since there is very little data, but as the database grows, you may start to experience inefficiencies and poor performance. Some of the seven most common mistakes that database professionals make include not spending enough (or any) time on documentation, little or no normalization, building before designing, improper storage of reference data, not using foreign keys or constraints, not using naming standards, and improperly choosing primary keys.

In chapter 2, we learned the basics of modeling rules in database design. It is important for us to define business rules and definitions during the design phase so that we can keep the database consistent. We also learned about primary keys and when and how to choose them. It was good to see the article reinforce the many topics that we covered. There were some items that we haven’t discussed in class yet, such as normalization (week 4) and reference data, but I’m sure that the article exhibits the same point of view.

When I just started working with databases and creating my own, I often built the database as I went along. I would add tables, attributes and relationships as they were needed during the coding process. This often led to making numerous database structure changes and many columns of duplicate data. I agree with the article that one should spend the time to design the database before actually building it to avoid such headaches. Documentation also helps as reference in future troubleshooting sessions.

Tiret, J., (February 16, 2010) Seven Deadly Sins of Database Design. Retrieved October 5, 2012 from http://esj.com/Articles/2010/02/16/Database-Design-Sins.aspx