Post reply

Replicate pending transactions manually

  • June 26, 2013 at 4:27 am

    #279168

    Hi all,

    I have configured the transactional replication between two servers which is different locations, it was working fine till now, but becuase of connectivity issue the replication is stopped and the new transactions are not getting updated on subscriber,

    Is there any way I can manually replicate the pending transactions to subscriber, I can access this server by remote desktop / team viewer.

    Is there any option available that I can transfer the pending transaction into a file, and upload it on subscriber ?

    Please help...

    Thanks

  • June 28, 2013 at 11:05 am

    #1628362

    I don't think there is a comfortable way to do this. Fix the connection and let the replication do it's job.

    Even if you woul transfer the commands manually, what if you fix the replication afterwards? Inserts of records would happen even if you already inserted them manually, resulting in primary key violations.

    Of course you could have a look at the table MSrepl_commands at the distributor, extract the pending commands, execute them manually, and delete them from the table. But I never would do this. It's a lot lot lot lot lot of work and you still have to be very very very cautios to not break the replication.

  • July 1, 2013 at 12:36 am

    #1628612

    Thanks for your suggestions and reply,

    Even I did the same recover the connection and replication did the job itself, I was just curious whether we have such options available or not !! in case the connections are not able to restore and the subscriber need the data fast.

  • July 1, 2013 at 12:49 am

    #1628613

    I see. I got in touch with these thougths several times with my own systems. If the subscriber get's offline "a long time" in my opinion there are 2 possibilities:

    1) just wait until pending commands are delivered

    2) reinitialize. But take care of what this means to your subscriber and your publisher. How large is the snapshot, what about the data already transferred to the subscriber (how to delete them) etc. This could be quite difficult and get the whole situation really really bad.

    Usually it's the best just to wait for the distribution agent doing it's job. Only thing you can do is have a look at the subscriber for ressource intensive processes that might slow down the database or the insert/update statements of the replication.

    All other tries usually make the whole situation worse or even force you reinitialize, whith all it's much of work.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply