Most of us who do database design do not adhere to the rules of normalization. Those of you who are new to programming and database:
| Quote: |
| Put simply, normalization is an attempt to make sure you do not destroy true data or create false data in your database. Errors are avoided by representing a fact in the database one way, one time, and in one place. Duplicate data is a problem as old as data processing. Efficient and accurate data processing relies on the minimizing redundant data and maximizing data integrity. Normalization and the Normal Forms (NF) are efforts to achieve these two core objectives of data processing. This article will examine the concept of normalization in-depth. |
What happens when you do not follow proper normalization of a database and be lax about you home work is that a lot of extra code gets written for areas that could be handled by the DBMS.
Everyone new to programming and database stuffs, whether it is Mysql, oracle, or MS Access read these two easy articles to get acquainted with database normalization.
[http://dev.mysql.com/tech-resources/articles/intro-to-normalization.html]
[http://www.devshed.com/c/a/Administration/Database-Normalization/]
_________________
Dust fills my eyes / Clouds roll by / and I roll with them / Centuries cry / Orders fly / and I fall again
Afford best design, implement best solution. Outsource your web design.
