Post reply

Multiple Client DBs and Multiple Instances

  • February 9, 2007 at 9:18 am

    #171345

    Hello everyone,

    I am asking for some more advice.  We are redesigning our current application which for performance reasons has 1 db per customer.  All of the databases have identical schemas.  We currently have approximately 500 customers but that will easily grow to over 5000 in the coming years.  I know that there are limits on the # of databases per instance and I want to design the model where the app can access multiple instances probably on different clusters seamlessly. 

    My idea is to have a 'Master' type database that redirects to the correct instance and db after login.  I am concerned with performance with this approach though.  We have a target requirement that all result sets should be returned from the db within 2 seconds.

    Thanks in advance for any advice.

    Keith

  • February 9, 2007 at 11:13 am

    #688928

    Not sure I would go that way, especially with SQL Server 2005.  You could go this direction: A "single database", partitioning the databased on the unique customer id.  To enhance this, partition the database horizontally over several servers as well (federated databases servers, see BOL).

    Just an idea that you may want to at least consider.

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

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