Post reply

Architecture Dilemma

  • June 8, 2009 at 2:28 pm

    #132739

    Hi Guys,

    I am designing a database architecture for a Health care product. The design should follow SAAS model.

    Here are the details:

    1. The system serves multiple customers who wants to keep the data separate for security purposes and other reasons.

    2. Each client will be sending the delta data daily after one time bulk data load.

    3. Need one common database the maintains the data for all the clients.

    4. Each client decides where the database should reside. Either with in my company's data center or with in their network.

    5. Each customer will be logging into the web site to check the data. At this time, we need to show only their data based on the login user. Each user will belong to one and only Customer.

    6. The design should be such a way that to add a new customer, it should not take too long of time. It should be simple to implement the system with new customers.

    7. Do not want to rewrite the SPs for each customer. Or atleast reduce the work.

    What is the BEST approach? considering Performance, Security, Maintenance, etc?

    Anybody anything similar to this? What are my options?

    Thanks a million in advance.

  • June 8, 2009 at 2:54 pm

    #1006316

    Please don't cross post.

    further discussion using http://www.sqlservercentral.com/Forums/FindPost730969.aspx


    Lutz
    A pessimist is an optimist with experience.

    How to get fast answers to your question[/url]
    How to post performance related questions[/url]
    Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply