• With this type of schema you have create a 1:1 relationship from Person to Address. You did not gain any of the advantages of normalization with this. You will 1 and only 1 row in the Address table for each Person. I would suggest to have an Address table with Person_ID, Addr1, Addr2, City, ST (and what ever fields for the physical address you need) and finally an AddressType column. This last column would tell you if this is the permanent, mailing, parents etc. This table should not have email. That should be in another table (PersonEmail or similar). This would have maybe 3 columns. Person_ID, EmailAddress, IsPrimary. This would allow to have as many email addresses as they want/need.

    _______________________________________________________________

    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/