Design a database with standarized and non standarized data coming from multiple clients SQL Server2008 R2
Hi,
I have a situation where I am tasked with my team to deveop a database for extranet sites which would represent multiple clients data. Now, important thing is there are two parts of incoming data from clients as follows;
1. Standarized Data: Which is common accross all existing and upcoming clients.
2. Client Specific Data: It varies client to client and contains client specific data columns.
Now, when designing database how to cater these two requirements;
1. Should I create new database for every client's extranet database in SQL Server 2008 R2 ?
2. OR Should I create only one common database to hold all clients data?
If I create only one database to store all clients data including standarized data and non standarized data then how this would be managed?
e.g.,
tbl_StandarizedAndNonStand
ID,Name,Description,Code,C
Can you please help me identify pros and cons of both type of implementations of database (means one database or new database for every new client)
Please let me know if you require further information.
Your comments and suggestions are greatly appreciated to solve this design issue.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks alot. This helps
Open in new window
This is an absolute no go.
Storing the data per client makes in many cases sense as it allows you easily to inspect it or track down data issues per client. But this must not be an extra database per client, it can be a single staging table per client or even a folder where you store the raw data. Depending on the number of clients and the amount of data you can also consider using one extra database where you store the clients data before you import it into your main system, e.g. separated by schema.