November 29, 2005 at 1:14 am
Hi ,
We're building a windows app and using SQL 2005.
The scenario is this.
Our app will be spread across various geographical locations.
The information is more or less location specific i.e. a user in one loaction will probably not require to see/modify the data in another location. We are looking at huge volumes of data and the connectivity could be pretty decent.
Do we
1. Go with one centralised server?
2. Go with a server for each location.
In this scenario what would be the impact on the cost.
3. Go with Point 2 but also have one centralised server which will sink up data from all locations. Is this suggested? If so does SQL server have some kind of automatic sync utility or services which can be say run at a particular time?
4. I do not have much info on Mirroring but will this help if I were to use a centralised server.?
Thanks in advance
Soni
November 30, 2005 at 6:54 am
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply