Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
maryam_80
Starting Member
1 Post |
 Posted - 2011-08-11 : 15:30:36
|
| Hi,We are implementing a web-based application for a company which owns 3 other company. At the first phase we suppose to deliver the software to just one of the sub company.Now, I was wondering what is the best way to design the database?1)Create just one database and keep all those 3 different company information in same place2)Create an instance of the database for each company (in this case 3 different instance of database)Also, we may need to make reports based on information we have for all those companies.Note: Each company could have different kind of information than othersThanks in advance |
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2011-08-25 : 09:13:54
|
| If possible go with #1.We have separate Databases and we spend a lot of time applying the same updates over and over to every Database. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-08-25 : 09:21:52
|
| I agree with denis, but in some cases, contracts or law may require that you keep them seperate.If you do keep them together, you need to be VERY careful not to expose one clients data to another. |
|
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2011-08-25 : 11:09:50
|
quote:
Originally posted by russell
I agree with denis, but in some cases, contracts or law may require that you keep them seperate.
Or if they are in different countries, a single Database could be a performance issue if the distance is great enough. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2011-08-25 : 11:24:20
|
| I'd recommend designing the databases so that they could accommodate all customers in a single DB, even if you keep them separate. That way you only have 1 "version" of the database schema, which is far easier to manage than if they diverge based on customer features. A company I used to work for started with a gold schema, but kept adding stuff on for each client's DB. Now they have 29 or so slightly different database structures that they cannot manage and may not be able to consolidate anymore. |
|
|
|
|
|
|
|
|
What's the best way to design same Database for di