Replicating Databases for Server OffLine
-
Hi all,
was looking for some advice as to which would be the best model for replicating databases to Server 1 which then would become available if Server 2 went offline and then have the changes come to Server 2 when it came back online again.
I thought Merge Replication would be the one to go with but thought I would see what everyone else thought.
Cheers
Angie
-
This was removed by the editor as SPAM
-
i'd go with merge . . . it's the most autonomous and best at synchronization. but, beware the complexities of this most elegant of replication models. it's for well designed app's/db's only and absolutely requires competent administration. app developers will bemoan it for immediately revealing their own deficiencies . . . it's not for db's requiring mass updates (snapshot is best here) . . . the dba must have the most intimate knowledge of how to handle a db under merge replication (usually during a pressure-cooker situation).
the caveats said, merge is my default choice . . . there must be an overriding reason to go with something else. if designed and managed right, it's effectiveness, efficiency, and reliability are outstanding.
-
Thank you for your reply. Much appreciated.
I had better make sure that I research the topic throughly before I do this.
Thankyou
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply