PDA

View Full Version : Database Design Normalization to 3NF


GeordieJon
January 18th, 2007, 09:52 PM
trying to understand how to do Normalization to 3NF. applying for a job, which involves having to do this. i have all the other requirements for the job are covered, just this is very new to me and is getting me confused.

we are to be tested in the interview in 4 weeks, and have been given some practice ones to try and do.

I understand how to get to 1NF, by putting extra lines in, so there are no duplicate entrys and only 1 piece of data in a cell. but how would i get this into 2NF ????

Managed to normalize the tables now thanks

http://img329.imageshack.us/img329/3651/normilizationvv5.jpg

much appricated if somebody could help me

degsy
January 19th, 2007, 10:05 AM
I'm not sure about the correct 3NF requirements, but you should normalize it to make it in to a relational database.

This means splitting up your table in to seperate tables so that you do not have duplicate data.
You associate tables/records to each other using Primary & Foreign keys.

e.g.
You can have a table for customers containing their name & phone number
You can have a table for sales assistants containing their name & phone number
You can have a table for parts containing the part number and description
You can have a table for orders that will include the date then joined data from customer, sales assistant and part.

You can also have an associative table to link parts and orders. This will make it fully relational instead of using a multivalue field.
Rule 2 - http://en.wikipedia.org/wiki/Codd's_12_rules

Here is a basic example of database normalization. It may not goto the extent that you require, but may give you the idea
http://computer-helpforum.com/asp/aspfree/database_normalization/database_normalization.asp

oracle128
January 20th, 2007, 05:41 PM
You can also have an associative table to link parts and orders. This will make it fully relational instead of using a multivalue field.This is required, it's 1NF criteria.