'Serving the Microsoft® Access
Community since 1997'

Free Samples
About Us




Database design theory includes data design standards called normal forms. The process of making your data and tables match these standards is called normalizing data, or normalization. By normalizing your data, you eliminate redundant info and organize your tables to make it easier to maintain the data and table structures.

There are five (5) normal forms, each addressing a specific problem with data organization.

(article continues after sponsor spot)

A table is in first normal form when each field contains the smallest meaningful value. The easiest example here is a field called name, which has the person's full name. NOPE. You need to split that into 2 fields; first name and last name.

A table is in second normal form when each non-key field is fully dependent on the primary key. (it must be in first normal form as well)

A table is in third normal form when each non-key field is nontransitively dependent on the primary key. (it must be in first and second normal forms as well)

Further details about normalization are beyond the scope of this site. There is, however, a 50 page eBook available that explains not only normalization, but also "denormalization". The eBook is not written by an academic, but by someone with over 20 years of data modelling experience while working for government, industrial, communications, and other large relational database customers.

Download "Database Normalization" from ClickBank today, by clicking here. It is a PDF file, approximately 480K in size.

More about the book "Database Normalization".

Understanding and mastering database normalization techniques is essential in order to achieve a high performance database design for your system. If your design doesn't conform to (at least) the 3rd Normal Form (3NF), chances are high that you will find it hard to achieve the performance needed for a successful application.

Furthermore, you will find that writing good SQL-statements (SELECT, UPDATE, INSERT or DELETE) is difficult, and sometimes actually impossible, without using a lot of procedural coding (PL/SQL in Oracle, VB/C# in Microsoft products).

Many "experts" will tell you that if you do normalization according to the 3NF, you're well off. This eBook proves the opposite, and is illustrated with graphical Entity Relationship examples.

This eBook will review the 5 Normal Forms in database normalization normally used to analyze data models in the making. There are 50 pages of quality, need-to-know information.

The examples, based on a consistent theme of accounts, departments, projects and transactions, help you to easily review the consequences as you are moved from 1NF to 5NF.

The book also discusses the pros and cons of denormalization, with the aim of improving performance, and studying the consequences denormalization may have on your database. It is illustrated with more than 20 entity relationship diagrams, as well as database (server) models, and SELECT statements that use the model.

Download "Database Normalization" from ClickBank today, by clicking here. It is a PDF file, approximately 480K in size.

Happy Coding

Note: This web site dedicated to MS Access database users is an independent publication of Richard W. Killey and is not affiliated with, nor has it been authorized, sponsored, or otherwise approved by Microsoft® Corporation.


© 2006, 2007, 2008 Richard W. Killey. All Rights Reserved. - Privacy Policy