I read in a previous post (comments by Hilary) about monitoring agents
closely to avoid reintialisations.
I'm sure we would all like to avoiding reinitialisations - some tips/reading
on how to effectively monitor the agents - what to do/look for etc - would
be a great help.
Thanks
Darren
I DTS or export the agents history and agents errors tables from my pull
subscriptions locally and then run queries against them to get a window into
my pull subscription agents activity.
Basically you want query the time column and compare this value against the
system time and see if the difference is greater than a day or whatever
interval you choose.
I cover this in great detail in my book.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Darren Wallace" <darren@.pcresources.com.au> wrote in message
news:uXmGioGmEHA.3712@.TK2MSFTNGP15.phx.gbl...
> I read in a previous post (comments by Hilary) about monitoring agents
> closely to avoid reintialisations.
> I'm sure we would all like to avoiding reinitialisations - some
tips/reading
> on how to effectively monitor the agents - what to do/look for etc - would
> be a great help.
> Thanks
> Darren
>
Friday, March 9, 2012
Monitoring agents to avoid reinitialisation
Labels:
agents,
agentsclosely,
avoid,
avoiding,
database,
hilary,
microsoft,
monitoring,
mysql,
oracle,
previous,
reinitialisation,
reintialisations,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment