Normalization

S

Sibes

I just read about normalization. and have some conflicting views about it.
Some say have many small tables for an effective database. Others say as
long as they relate to the Primary key they are ok one table.

I am confused.
Do i have many small tables or combine the tables where i can?

I hope someone can staigthen me out on this issue.

Thanks for your help.

Lisa
 
D

Douglas J Steele

The only answer is that fields belong in the appropriate table, and that's
what normalization is all about.

The fields that go in a particular table must be related strictly to that
table's primary key. If they're not, then they're in the wrong table.
 
A

Arvin Meyer

One table is NEVER OK unlist it's a small list like first name, last name,
and phone number. What is important is not the number of tables but how they
relate to each other. Normalization is about entities (tables) and
attributes (fields) fields are descriptors for the table. Orders do not go
in a company table, but a company address does. If the companies have
multiple addresses, they need an address table. Products have attributes
like quantity, color, size, but those fields belong in the product table.
Color and size do not belong in the orders table if they are also in the
products table. Have a look at the following:

http://www.formeremortals.com/Downloads/UnderstandingNormalization.pdf
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access
 
G

George Nicholson

One table is NEVER OK unlist it's a small list like first name, last name,
and phone number.
Click to expand...

No real argument except that who has only 1, (or 2) phone number these days?
A separate PhoneNumbers table has become pretty much standard procedure.
 
Top