This is only an introduction to the subject of normalization. The topic is extensive. For those of you who are developing databases on a day to day basis, knowing how to formally normalize a table can save large amounts of time in the long run. Being able to determine what level of normalization a database needs and designing to that level of normalization can be difficult in larger applications and will often have many possible solutions. Education and experience are the tools you will need to design efficient databases with minimal (or, in a dream, no) anomalies. I hope this introduction to normalization is helpful to the readers, and I intend to publish a future article covering denormalization and case studies of some database and the way in which they were normalized.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 94 
