Database design for recruitment company

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • DaveRook
    New Member
    • Jul 2007
    • 147

    #1

    Database design for recruitment company

    Hello

    I am designing a database to hold client details for a recruitment company.

    All the data will be uploaded via a website

    I will need the following information in 1 table

    UniqueID - Name - ContractType - JobType

    Please note, ContractType (whether they want to work perm. or temp.) and JobType (such as what industry(ies) they want to work in) can have multiple options.

    What is the best way to approach this? Should I split this into 3 tables (one for personal information, one for ContractType and one for JobType) or should I try to force it all into one (although this will be a nightmare as I don't know how many job types will be offered)?

    Ultimately, I want to display results for each person on my website so don't want to open mulitiple connections for each database (unless that is the best way forward)

    Dave
  • ck9663
    Recognized Expert Specialist
    • Jun 2007
    • 2878

    #2
    Your question is more of a database design fundamentals, not specific to SQL Server.

    Try to start from here.

    Good Luck!!!

    ~~ CK

    Comment

    Working...