database design

Hi,

I've got a series of entities with a fairly complex set of relationships :

                               Reason


                                 |

                                 N


                                 |

Industry -1-----N-\              |
                   - Company -N-----N- Title
Sector   -1-----N-/              |


                                 |

                                 N


                                 |

                               Issue

which state that each company (in a specific industry and sector) may have n titles associated with it, and each title - company relation may have n issues and each title - company - issue relation may have n reasons. (I hope I've got all of that bit correct!) I've got five tables representing industry, sector, company, reason, title and issue and a table representing the relationship between company, title, issue and reason.
Now the question I've got concerns the final linking table. It has four fields : CompanyID, TitleID, IssueID, ReasonID and a multipart primary key consisting of all four fields.
Is this a good way to go about things? It seems the obvious way to me, but I'm a little worried about performance both on INSERT / UPDATE queries and SELECT ... FROM ... INNER JOIN queries which would be nested to allow me to do things like :
find all issues for CEOs in Automotive Manufacturing or
find all titles in Automotive Manufacturing with a particular issue. Has anyone any ideas / experience?

Thanks in advance,
regards

James Received on Tue Jun 27 2000 - 00:00:00 CEST