Hi. We have replication setup from a sql server 200 database to a
sybase database on Solaris. Every now and then, the sql server
replication process will run into a deadlock with other processes on
the sybase side and be chosen as the rollback victim. The rollback
causes the entire replication to go down, and we have to manually
bring it back up. Does anyone know how to set the re-try parameter for
the replication so that upon being rolled back, it will automatically
re-connect to sybase to continue with the replication ? Thanks.
Steve,
if you are using merge replication, restarting the merge agent should fix
the issue. If you want this to happen automatically, you can force the merge
agent's steps to run in a continuous loop (step 3 -> step 2).
HTH,
Paul Ibison
|||loop back to step 1. I believe that in order for for detection of non logged
agent shutdown you must loopback to step one.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23$lpmAdZEHA.3092@.tk2msftngp13.phx.gbl...
> Steve,
> if you are using merge replication, restarting the merge agent should fix
> the issue. If you want this to happen automatically, you can force the
merge
> agent's steps to run in a continuous loop (step 3 -> step 2).
> HTH,
> Paul Ibison
>
|||Thanks Hilary,
step 3 -> step 1 is what I should have written.
Regards,
Paul
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment