Normalisation versus optimisation
From: Edward64 <edward.collier_at_techop.co.uk>
Date: 25 Oct 2001 07:16:40 -0700
Message-ID: <74bed22a.0110250616.7887c6d7_at_posting.google.com>
Three tables: ProductType, ProductVariant and DespatchNumber.
DespatchNumberID, (PRIMARY KEY)
DespatchNumberDescription
ProductVariantID (FOREIGN KEY on ProductVariant TABLE)
Date: 25 Oct 2001 07:16:40 -0700
Message-ID: <74bed22a.0110250616.7887c6d7_at_posting.google.com>
Three tables: ProductType, ProductVariant and DespatchNumber.
They enjoy a 1:n relationship, left to right e.g.
ProductType -> ProductVariant, ProductVariant -> DespatchNumber
The design of the tables is simple enough:
ProductType =
ProductTypeID, (PRIMARY KEY)
ProductTypeDescription
ProductVariant =
ProductVariantID, (PRIMARY KEY)
ProductVariantDescription,
DespatchNumber =
DespatchNumberID, (PRIMARY KEY)
DespatchNumberDescription
ProductVariantID (FOREIGN KEY on ProductVariant TABLE)
My question is this. Should I include the following column in DespatchNumber table:
ProductTypeID (FOREIGN KEY on ProductType TABLE)
Is there any upside or downside to this? Normalisation versus optimisation.
The target database is SLQ Server 7.0
TIA