Normalization speaker notes
This presentation deals with the concepts of relational databases and third normal form.
You should definately read about this either in the text that comes with the course, in the sources on the Web or in some other database book.
These are not technical definitions. They are the words as I see them. Your text will give much more formal and proper definitions.
These definitions can definitely be stated more formally and probably more correctly. Please check you textbook for the technically correct definition.
The first step in getting a database into third normal form is to determine the data that you need.
A well designed relational database will meet the rules of third normal form.
The previous slide show dealt with one to one, one to many and many to many relationships. These are key concepts in establishing a relational database in third normal form.
This is now in first normal form.
Before we can check for second normal form, we need to consider the primary key.
Second normal form says that information cannot be dependent on only one part of the primary key.
This is now in third normal form since it meets all of the rules for normalization.
This did not break the third normal form rule so we are done.
Example to show third normal form manipulation.
We have ended up with three tables (four if we consider the contact information as part of the data we want to keep). These are the tables that we would create in Oracle.