Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

single database or multiple database

Status
Not open for further replies.

balachander

Programmer
Aug 17, 2001
2
IN
I need some clarification to design the database of my project.Let me explain my project first.
This project has atleast 10 clients who are going to update the database.
Each client has 1 million records per year.Each client has similar kind of data and each client has nearly 10 tables.

I have decided to choose any of the three possible approaches for this DB design

1. Keeping a single table (with Client ID field)for all the clients(single table - single database)
2. Keeping seperate table for each client in a single database (Multiple table - single database)
3. Keeping separate database for each client (Multiple table - multiple database)


Let me know which is the best appraoach among the above three for my project.I am using SQL server 2000 as database server.Currently we have only one database server.In future, we may go for more than one database server.Even we can go for the federated database system.My query is mostly based on the client wise, but occasionally I need to query the data by combining the more than one client.
So please help me to find the best of above three approaches for the current situations which will give good performance now and the porting to federated database system can also be easily implemented in future.

Can any one help me?

Thanx in advance,
Bala
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top