Regarding Database Design

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Ramanish
    New Member
    • Dec 2007
    • 1

    Regarding Database Design

    Hello,
    Me and my team get indulged in developing web based help desk tool.For that we have analyzed so many product for feature identification. Still a doubt is unsolved .

    My doubt
    -----------
    if a company 'A' subscribe a help desk tool for 10 users for 1 year and other company
    'B' subscribe the same help desk for 10 users for 1 year. In this scenario how the Product development company designed its database to serve.

    Our thought
    --------------
    We tried to handle separate schema for every company (Group of users) .In the above scenario our plan is to handle two schema one for company 'A' and other for company 'B'. We tried this using hibernate, still we can't achieve the result.

    Request
    ----------
    What is the feasible way to handle database in such scenario.In the online market so many products are web based .Actually how they are having their database.
  • debasisdas
    Recognized Expert Expert
    • Dec 2006
    • 8119

    #2
    Creating separate schema for individual users is not at a solution.
    As the number of company increses how many schemas you will create.

    You need to store the comanyname in a master table and store the corresponding usernames in a detailed table.

    Comment

    • MMcCarthy
      Recognized Expert MVP
      • Aug 2006
      • 14387

      #3
      Have a look at this tutorial on database design.

      Database Normalization and Table structures

      Comment

      Working...