Post reply

Using SQL in Application Service Provider Env.

  • December 15, 2003 at 12:23 pm

    #83686

    We're working on a new application for a client who's deploying it as a web services portal. Expected accounts is 3000+ (user groups). Each account will probably require its own database. Does anyone have a "best practices" or "how-to" information for this type of project? We have experience with building ASP using SQL, but want to confirm what we're doing with others...

  • December 15, 2003 at 1:14 pm

    #486251

    Why does each account need its own database?

  • December 15, 2003 at 1:55 pm

    #486259

    quote:

    Why does each account need its own database?

    Each account represents a separate company. If we didn't separate each company's data by creating databases then we run into 2 problems:

    1. We have to have additional columns in each table specifying what company the data belongs to and

    2. For security reasons, there is a "chance" that if someone breaks into the DB, they will have access to all data as opposed to a single company's information.

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

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