Re: SQL 2005 Repl. Agent seems to stall randomly

There was a condition on SQL Server 2000 which was similar to this. You had
to reboot to solve it. It was due to depleted buffers from what I
understand.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Jeremy Hannon" <Jeremy.Hannon@xxxxxxx> wrote in message
news:%23DlFW3TbGHA.3444@xxxxxxxxxxxxxxxxxxxxxxx
I am encountering an issue where, with several different replications
occurring, the agent jobs start but never really seem to do anything with
the second job step.

They say they are running, but they don't do anything. Restarting SQL
Agent causes them to work, but then other replications jobs seem to have
the problem.

Even with the jobs "stalled", the task (log reader, or distib.exe) will
work fine if I run them from command prompt with the same parameters.

This is transactional replication from about 10 dbs, each with 2
subscribers.

I came across this article ( http://support.microsoft.com/?kbid=306457 )
for SQL 2000, and this one (
http://www.microsoft.com/technet/prodtechnol/sql/2005/newsqlagent.mspx )
where it says the registry keys are still used, but they don't seem to
exist and adding them seems to have no effect.

Any ideas?


.

Relevant Pages