Re: Help with Database design

Oh Dear God....

Please let the Modellers alone. they have done the right thing.

I have seen many many projects doomed to fail because of people who think all data should be in one table to avoid a join...

If you cant stand typing a long query, then make a view. It wont be too slow. If it gets slow, tell the DBA to optimize it for you.

randy

Eric wrote:
>
> 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 Mon Nov 01 1999 - 15:48:00 CST