October 14, 2005 at 7:47 am
I have two databases for which I wish to establish replication. The schemas are the same, but data is different. I am setting up merge replication. I do not want to apply the snapshot from the publisher but I do want to merge the differences between the two databases so that after the merge replication, the two databases will be equal. The current process we have established is to backup the database that is to become the subscriber, and restore to the publisher database so that at the time that the publication is created, the two databases are in sync. Is there a way to do this without backing up the subscriber and restoring to the publisher?
Gordon Pollokoff
"Wile E. is my reality, Bugs Bunny is my goal" - Chuck Jones
October 14, 2005 at 9:58 am
Are you setting up merge replication just to get the databases to be the same ? Backup & restore sounds the simplest solution to me.
After they are the same, then what will you be replicating ??
October 14, 2005 at 11:06 am
Perhaps a move from the general to the specific......
I have a merge replication setup between two servers.....For reasons that I cannot explain (as in, huh...what happend?!?) the merge agent no longer exists between the two databases. I want to re-establish the replication (the subscriber still has all the replication tables, views, triggers etc). Will simply recreating the subscription resolve the problem, or is there another way. Others here have suggested that I would need to copy the subscriber to the publisher (backup/restore process) than recreate the publication and the subscription. This just doesn't seem right.
Gordon Pollokoff
"Wile E. is my reality, Bugs Bunny is my goal" - Chuck Jones
October 14, 2005 at 2:45 pm
I've only used Trans & Snapshot ... so I can't be much help with Merge. Since you're using Merge, I assume you have updates that occur at the publisher & at the subscriber that need to be kept in sync with each other ?? If you do a restore of one to the other, then that means that one db must be the "good" db, but then you'll lose updates that have happened at the restored db.
Perhaps you could set up some test databases with a small sub-set of data to test different things.
October 14, 2005 at 5:00 pm
If you mean just the REPL-Merge job has disappeared but the Publisher, Distributor and Subscriber DBs are all in place as it was, then you should be able to just script the REPL-Merge job creation and it should pick up where it left off. I have had to do that before and it worked fine.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply