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 |
|
Kaleem021
Starting Member
26 Posts |
 Posted - 2005-04-04 : 02:17:58
|
| Dear All, I am designing an application for a company that have three branches in the same building(Lan is being used to connect them). Front end will be the same for all three branches (as they do the same business). Question is that should I create three databases, one for each branch, or create one database and add a field 'Branch_Code' to distinguish them. Usually no branch is concerned with other's data.A quick reply will be highly appriciated.Thanks.Doing Nothing Is Very Hard To Do, You Never Know When You Are Finished. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-04-04 : 03:35:10
|
| Up to you.I would go with the single database unless there is a reason not to as it's easier to administer.It's best to allow for the possibility even if you don't use it in case you get a lot of tiny branches later.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-04-04 : 08:23:47
|
| Independance of operations may dictate your implementation....ie if one branch wants to restore data without affecting others....or if performance (or storage+processing costs) needs to be strictly controlled per branch, then seperate databases may be needed. |
|
|
|
Kaleem021
Starting Member
26 Posts |
Posted - 2005-04-04 : 10:02:47
|
| Thanks nr and Andrew Murphy for your comments. I am going to create three databases as any branch might ask to restore database.Doing Nothing Is Very Hard To Do, You Never Know When You Are Finished. |
|
|
|
Arti
Starting Member
5 Posts |
Posted - 2005-04-04 : 13:02:16
|
| I think by this time you must have created three databases. But while thinking about your question A point came into my mind - if in future you need to get more funcationality in your application (want to put more columns or some business rules) - then it will be really hard to maintain same thing at three different places. Both ways have prons and cons - you will be the best judge as you know the situation!!!!! |
|
|
|
Kaleem021
Starting Member
26 Posts |
Posted - 2005-04-05 : 01:20:41
|
| Yes Arti, you are right but if one branch changes its business rules then I can easily change the database accordingly.Doing Nothing Is Very Hard To Do, You Never Know When You Are Finished. |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-05 : 01:22:28
|
| Then you have multiple versions of databases to manage. I hope you have good documentation and control over your business processes.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Databse Design Issue