I am laying out the specs for a new DB for our company that will track applications that our offices receive. I am at a point in the table layout that I need an outside opinion. I hope this is clear and concise:
Our company has 4 branches that handle different types of insurance. 90% of our applications will be processed by only one branch. The other 10% of applications will need several types of insurance and be split between any combination of the remaining three branches.
For an application that is split, any one branch wants the ability to see on one form what the other branches are doing with it via an [Action] or [Status] field. I have attached two versions of the database structure. My gut tells me that Version 1 is the way to go, but I just wanted to check with the experts. I also want to make sure that I have the multi-field keys set up correctly. I know there is also debate on how one’s keys should be set up. Thanks for your help.
Our company has 4 branches that handle different types of insurance. 90% of our applications will be processed by only one branch. The other 10% of applications will need several types of insurance and be split between any combination of the remaining three branches.
For an application that is split, any one branch wants the ability to see on one form what the other branches are doing with it via an [Action] or [Status] field. I have attached two versions of the database structure. My gut tells me that Version 1 is the way to go, but I just wanted to check with the experts. I also want to make sure that I have the multi-field keys set up correctly. I know there is also debate on how one’s keys should be set up. Thanks for your help.
