Re: SQL Database design question

If you control the stored procedure layer into your database, this won't be an issue -- just make sure that the SP that inserts/updates the Employee records, also inserts and updates your Employee-Branch intersection table. This is a classic many-to-many relationship, and there's no reason in the world to model it in any way except with the intersection (or junction, if you like) table.

This does require you to have some control over the processes that are touching & updating your table structures. If you're going through an SP layer, this problem simply doesn't exist. If you're not, you should be. Received on Sat Jan 29 2005 - 02:05:51 CET