Normalized Table Design

Edgar F. Codd put a lot of thought into how to relate one Table to another. Codd, who received a PhD in 1965 from the University of Michigan, Ann Arbor, defined the concept of normalization in 1970. Here is a brief summary of his concepts.

 

There are a few rules that define a good relational database. Each rule is called a Normal Form. Each rule, or form, is more restrictive. There are six Normal Forms.

 

Normalizing a database defines the Table design and how Tables are related.

 

The rules are simple:

Minimize duplicate data

Protect the data integrity

 

Purpose: No repeating groups or redundant data.
 

Process: Usually, big Tables are reduced to smaller, functional Tables. There should be a separate Table for each collection.

Example of a Table in Microsoft Access

Exam 77-885: Microsoft Access 2010

2. Building Tables

2.1.1. Create tables in Design View: Create Tables that do not have repeating groups