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 |
|
MrRanger95
Starting Member
1 Post |
 Posted - 2012-08-06 : 11:45:58
|
| I have written several projects using different SQL servers (Microsoft, MySql, Oracle), but in the past I have not been in charge or of setting up the server or database myself. I would be given a blank database and then build the tables within it and the applications that connected to it. I am now working a new place and we are looking to move our current systems, which uses files to store the data to an online application using an sql server. In the past when I wrote applications they were for only one set of users. The company I work for now we will be developing and maintaining different custom applications for our clients. We also will want to and outside provider to host the sql server. My main questions are should i use a different database for each client, or develop a table set that allow more than one client per database. Secondly with using and outside provider to host which of these 2 option is the most secure and or cost effective?Any information or remarks will be appreciated. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-08-06 : 14:23:23
|
quote:
My main questions are should i use a different database for each client, or develop a table set that allow more than one client per database.
Generally speaking you are better off with the 2nd option (multiple clients per database), it is much easier to branch from that than trying to consolidate multiple different databases into one, should you be forced to do that. This also means that each table can support multiple clients as well; one table per client is probably worse than one client per database. |
 |
|
|
|
|
|
Database Structure