• I would agree that a many to many is not a the way I would choose here. There is nothing to be gained by this. Yes it is possible that you can have multiple contacts with the same phone number. For this type of thing a small amount of data redundancy is not a big deal.

    I understand what you are saying that you want to allow for as many phone numbers for a given person as they want. What I don't understand is how that creates orphans. I would establish that a foreign key with cascading delete. That way if you delete the contact, all of their phone numbers get deleted too.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/