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 |
|
KnooKie
Aged Yak Warrior
623 Posts |
 Posted - 2002-05-08 : 06:59:13
|
| I'm hoping someone can help shed an experienced light on this.We are currently using SQL7 and have been happily doing transactional replication (one-way) for a few years from London to NY.In around a months time i am going to be asked to go to New York to discuss the implications/possibilities of implementing bi-directional replication between London and New York. My question is can anyone give me any advice as to what i should bare in mind with regards to bi-directional replication ?? I have not implemented it before. Any 'must have' books ? (Although i underdstand Ken Henderson's doesn't cover much replication - sry Rob)We will in all probability use SQL2K for this and upgrading to it is not a problem.The database involved is not big, only around 1GB (Around 100 tables in schema size).The number of users each side of the pond is roughly the same but not large (perhaps only 20 at each site).The database will also be equally transactional from both sites with transactional levels high for the number of users.Is merge replication the best option for this scenario ?I am aware of the need for a test environment prior to implementation to mimic the scenario.Are there any angles i am missing ?Any other info needed just post here and i'll add it if i know it.many thanksPaul |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2002-05-08 : 07:08:36
|
| >> Is merge replication the best option for this scenario ? Paul, depends on what exactly are your requirements. Will you be updating the same rows from the same table at both sides? Or are you publishing different tables from both ends? Obviously, merge replication is a bit complicated than transactional and needs thorough understanding and testing before going live. Also, in SQL Server Books Online, there is a sample available, that shows you how to setup, bi-directional, transactional replication..did you have a look?As far as books, there aren't any that I know of, that deal exclusively with replication.--HTH,Vyashttp://vyaskn.tripod.com |
 |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-05-08 : 07:19:10
|
| Yes potentially same rows will be updated from both sites.Exactly the same tables published from both ends (if that's how it works) and used at both ends.Essentially both sites will be doing exactly the same thing with the same tables and using the same front-end.I will look in BOL nowthanksPaul |
|
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-05-08 : 09:32:01
|
| There's always an angle you can, and hopefully you're not going to, miss.Merge replication is one of the most trickiest things I know in MSSQL. In many cases this kind of replication requires a front and back-end change, too.There is quite a lot in BOL (in theory) but the best way is to experiment a little.GOOD LUCK! |
|
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-05-08 : 12:49:15
|
| With around 20 users each side of the pond does anyone have any hardware recommendations ? i.e. Server specsPaul |
|
|
|
|
|
|
|
|
Bi-Directional Replication Advice....