Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Help with Database design
Another option you may want to look at is to create another table that has
all the primary information from all the child tables. Therfore an insert
into email or phone would fire a trigger and the current version of the
record would be updated into the curr_cust table.
HTH
scott.
Eric <admin_at_t10.net> wrote in message
news:WGJS3.40$Pf3.6406_at_news.uswest.net...
> 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 Sun Oct 31 1999 - 10:12:20 CST