I’m struggling on how to map out the model for a database I’m looking to build. I’ll be using SQL2LINQ in C# once I have the database modeled correctly.
The first part that I’m looking at is designing the SQL Tables for distribution lists.
These DL seem quite complex as the following rules apply :
- There are three different types of DLs (Used for specific events).
- Each type of DL will contain multiple DLs (can be more than 10).
- A person can be in all three different types of DL.
- A person can be in multiple DLs of the same type.
For the person, I will be holding information such as :
- Forename
- Surname
- Contact Number
- Email Address
What I dont like is the idea of duplicating information, having the same person in the database multiple times; that seems not so clean.
Any help would be greatly appreciated, I can’t quite wrap my head around the best way to do this.
It sounds as if you just want a many-to-many relationship between people and distribution lists, which you can model with a junction table:
Person
DistributionListEntries
DistributionList
You could either store the
Typedirectly in the distribution list table, or have this as a foreign key to aDistributionListTypestable with additional information about the distribution list type.