Re: Newbie question about db normalization theory: redundant keys OK?

From: -CELKO- <jcelko212_at_earthlink.net>
Date: Fri, 14 Dec 2007 16:06:44 -0800 (PST)
Message-ID: <f5d4d682-b74f-4639-996b-686b101d3639@s19g2000prg.googlegroups.com>

>> Celko what do you think of 1NF, 2NF, 3NF as programming exercises? <<

A lot of it is common sense made formal. Ask yourself what are the things in your data model -- a lot of them will be physical (customers, goods, trains, cars, etc.) A lot of them will be relationships among (not always between!) entities (customer buys goods) and have a name of their own (sales). And somethings will be fuzzy, which is where things are tricky.

>> but getting a dB into 3NF form if it's in 2NF or 1NF form is a bit of work, agreed? The U of Texas example was easy to follow but in the real world I doubt it's so cut and dry. <<

The bad news is that it is a bitch to refactor a bad RDBMS design ..

>> Keep in mind I have a few days experience in this matter, but I think I'm on the right track with the above statement. <<

You're very well, grasshopper :) Received on Fri Dec 14 2007 - 18:06:44 CST