MultiUsers Question

Apr 3, 2006

We had a debate on designing a database .The use case is;

an application that we will rent to other companies from our own datacenter on the web.They will all use the same database schema.We found 3 alternatives for our solution.But we are not sure which one is the best.

We are expecting 20.000 insurance agencies to use the database composed of 33 tables.And they will all have their unique data but sometimes for reporting we might union their data.

ALTERNATIVES

1.Make 20.000 database instances.Every agency will have their own database instance.

2.Make one database instance , put a database ownerID(int) field to every table.And use appropiate indexes.*or table partioning

3.Make one database instance , and create 33 tables for every database owner.So total number of tables in the datase equals to numberofUsers X 33


Did anyone tested this situation?


*an article I read on the web said partining is allowed to 1000 per table and it is slow in SQL 2005.(I am confused)

http://www.sqljunkies.com/Article/F4920050-6C63-4109-93FF-C2B7EB0A5835.scuk

View 6 Replies


ADVERTISEMENT

MultiUsers Question

Apr 4, 2006

We had a debate on designing a database .The use case is;


an application that we will rent to other companies from our own datacenter on the web.They will all use the same database schema.We found 3 alternatives for our solution.But we are not sure which one is the best.

We
are expecting 20.000 insurance agencies to use the database composed of
33 tables.And they will all have their unique data but sometimes for
reporting we might union their data.

ALTERNATIVES

1.Make 20.000 database instances.Every agency will have their own database instance.

2.Make one database instance , put a database ownerID(int) field to every table.And use appropiate indexes.*or table partioning

3.Make
one database instance , and create 33 tables for every database
owner.So total number of tables in the datase equals to numberofUsers X
33


Did anyone tested this situation?



*an article I read on the web said partining is allowed to 1000 per table and it is slow in SQL 2005.(I am confused)


http://www.sqljunkies.com/Article/F4920050-6C63-4109-93FF-C2B7EB0A5835.scuk

View 1 Replies View Related

Develop Multiusers Applications With SQL Server Express

Feb 3, 2006

Can I develop applications with SQL Server Express that I have more than one user in several computers working with the same database on a server, or I can only develop applications with only one user with a local database with SQL Server Express?

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved