When we start multiple publications at the same time on the same publisher
and even against different published datatabases, at times, we run into
deadlocks and start all over again. This was in 2000.
Do we know, if in 2005, the chances of deadlocks are minimized if i start
multiple publications at the same time?
Its on the publisher. We want to run multiple publications at the same time
to save the time we are down.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:Oh2GCVD2HHA.1124@.TK2MSFTNGP06.phx.gbl...
> Hassan - never experienced this myself. Presumably the deadlocks are on
> the subscriber? One possibility is that having a remote distributor might
> help, although I'd like to know about the source of the deadlocks. Any
> ideas of the source - perhaps the cleanup agent running at the same time
> as the distribution agent if the problem is on the publisher. Staggering
> the executions in this case should be sufficient (if practical).
> HTH,
> Paul Ibison
>
Monday, February 20, 2012
Preventing deadlocks
Labels:
database,
datatabases,
deadlocks,
microsoft,
multiple,
mysql,
oracle,
preventing,
publications,
published,
publisherand,
run,
server,
sql,
time
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment