Re: Help with Database design

If history is required, it may be possible to introduce a start and end date into the primary key.
It's a well used concept for modelling data warehouse slow changing dimensions.

just my 2p

neil

Eric wrote in message ...
>I am a new employee at this company and I need help
>in explaining to the Data Modelers that their designs are not good.
>
>They will take a customer table and split it out into:
>customer
>email
>phone
>address
>etc...
>
>So when queries take place, a 5+ table join must occur.
>Does anyone have any quick stats on the overheads of joins?
>They tell me they split this up because they need to store history.
>
>How can I explain this to them that they need 1 customer table
>and maybe a history table. (since the history hardly ever gets queried)
>
>Thanks in advance!
>
>
>
>
Received on Tue Nov 02 1999 - 09:24:08 CST