Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2004
    Posts
    8

    Unanswered: Recommended DB Design

    Let's say for instance that you have a group of tables that stores address information for different groups (i.e. Doctors, Patients, Providers, etc.) Would it be better to create each table to store the address information or create an Address table that would store this information with an Address type and a link back to each table?

    I prefer the second choice, but am having a hard time convincing other devlopers to follow this route. Maybe if I have some input from a more experienced users group I can stress my point a little more effectively. Thanks in advance for any input you can provide.

  2. #2
    Join Date
    Dec 2003
    Posts
    454
    Why don't you store the address into the table Doctors, Patients, Providers?

  3. #3
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    You should consider going one farther and consolidating Doctors, Patients, and Providers into a single table.

    After all, couldn't a doctor conceivably be a patient of another doctor?

    You use a flag to indicate whether a particular person is a Doctor, and another to indicate whether they are a Provider.

    Then add a table to establish many-to-many relationships between the different entities.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •