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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2003-01-23 : 08:36:22
|
| Swaminathan writes "Hi ,We have an application running in Sanjose.Its being accessed in SJ, chennai and pune. Mostly its slow and sometimes we are not able to access the app when the network is down.We have decided to db replication in chennai.I read the article on choosing replication typein SQL team. But I am not able to choose the best replication type for us.we need to consider 2 things 1. db updation is very frequent.2. we should able to work even when the network(between US and india office) is down.we are using SQL Server 2000Looking fwd to get some input on this.Thanks in advanceSwami" |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2003-01-23 : 09:10:19
|
| perhaps the first thing to consider is do all sites that need to access the data also need to change the data ? If yes then merge or transactional with immediate updating subscribers is your best bet. Test scenario first to iron out inevitable teething problems though. I have not actually needed to try this method so perhaps someone else will touch on this greater than i. Search this site for a wealth of info on it as well. If no then transactional is your best bet. Bare in mind with this option that the data at the site publishing the database is the only place where it can be changed (without using external methods and lots of coding). The other sites will only be able to read the data NOT change it.If you publish from US to India and the network is down and thus affecting replication then India would NOT see changes made to data in the US until the network is back up. The US would be fine though. When the network came back up all changes made in the US would replicate to India and they would then be OK again. Again with merge replication there may be a way around this ?===========Paul |
 |
|
|
|
|
|