sql server replication: Log Reader Agent won't start without a lot of stopping/restarting -- sql server replication

Log Reader Agent won't start without a lot of stopping/restarting

Need more Zzzz
12/7/2004 5:29:01 PM

sql server replication: We are using transactional replication with concurrent snapshots. Publisher
and Distributor are on separate machines. Distributor and Subscriber are the
same sql server.

Initially, we didn't run into problems. But after adding more publications
and subscribers we've seem to run into some threshold where now with each new
additional publication, the log reader agent either gets stuck in the
starting state or eventual gets the agent is suspect warning. After stopping
and restarting the agent several times, we eventually get it to run, and from
then on, the agent is fine.

We currently have around 43 publications (each with one subscriber) running.
Resources (cpu/memory) seem fine on the computers.

Any ideas? Is there an limitation to the number of publications &
subscribers per distributor/replication setup?

Thanks.

Re: Log Reader Agent won't start without a lot of stopping/restarting

Hilary Cotter
12/8/2004 8:01:33 AM

Change your inactivity level to something larger. Right click on Replication
Monitor, select Refresh Rate and Settings and change it there. Change your
ReadBatchSize to something smaller, right click on your log reader agent,
select Agent properites, Steps, Run Agent, and then select Edit and at the
end of the string press the space bar and type -ReadBatchSize 50.

After your log reader agent has read the log and caught up stop your agent
and remove this setting.

Is your TLog huge?

--
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html

[quoted text, click to view]