June 9, 2006 at 12:11 pm
This is simple, but hard to explain
System is for printing bardcoded serial numbers on finished products.
a product can have 3 different part numbers:
PartNumber - Used during manufacturing
OEMPartNumber - What the customer calls the product
SKU Number - Stock Keeping Unit number, and what its sold on internet as.
In order to print the serial numbers, need SQL to keep track of what ones have been printed, based on PartNumber in a table called ProfileMaster. One record for each part. Contains things like Layout Format, any WEEE, RoHS logo's, all that jazz.
The question is, should this ProfileMaster table contain all the other part numbers too? OR should I set up a 1 to 1 relationship with another table called something like SuperPartNumberMaster that only contains all the different numbers for a product along with description.
I know 1000 records isn't that many, but like to stay close with something logical.
Dan
June 12, 2006 at 6:08 am
I think the important point about the views on normalisation is to implement what works for you.
You'd normally consider normalisation at the design stage and then modify the schema for physical deployment. The more you normalise the more joins you get. On the other hand there's nothing worse than loads of duplicated entries in a table!!
The other point is "if it ain't broke don't fix it"
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply