May 13, 2002 at 3:31 am
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. The schema is also identical for both sites.
Is merge replication the best option for this scenario ? From what i've read so far i believe so.
I am aware of the need for a test environment prior to implementation.
Are there any angles i am missing ? Anything i would be wise to know ?
Any other info needed just post here and i'll add it if i know it.
many thanks
Paul
Paul
May 13, 2002 at 6:10 am
Merge would be ok, as would transaction with immediate update/queued updated.
Andy
May 13, 2002 at 6:21 am
I agree with ANdy and suggest if the changes move quickly is important look at updating subscribers option.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply