Re: Design question

Given the little amount of information provided on your requirements (Cardinalities and entities are not sufficient to describe requirements), I doubt any serious design advice can be given to you.

A helpful way to help is to encourage you to read more about design issues and understand RM concepts.

Check...Introduction to Database Systems (CJ Date) is helpful.

Good luck in your efforts...Hope this helps...

disturbedOne wrote:
> Hi all, not sure this is right group. Hoping someone could give me so
> advice on my database design.
>
> What is the best way to join these tables
>
> Short version goes like this....
>
> I have tables : Person or Employee, Dependent (person is fk in dep
> table) then I have a bunch of tables related to insurance
> policies/events
>
> what is the best way to join these two together given this scenario
>
> A person can be an insured with many covered dependents on one policy
> A person can be insured with one or more policies
> A dependent can be the only insured policy holder but we must know what
> employee this relates back to.
>
> I was thinking an insured persons table with person id and dependent id
> - but this bothers me for some reason....any suggestions?
>
> Hope this was clear....
>
> Thanks in advance for your time!
Received on Thu Aug 03 2006 - 11:21:38 CEST