How can i make my log reader agent fast ? it take so long to complete
writing to the distribution database

Change the pollinginterval to something small, and set the readbatchsize to
something large (ie 1000). Study the impact of raising readbatchsize on
write performance. Also have a look at replication the execution of stored
procedures. This works best when replicating transactions via a stored
procedure which affect a large number of rows.

Also what is your commitbatchsize?

What these two commands do is to buffer the transactions in memory and shoot
them to the distribution database in increments. So with read batch size you
control how many transactions are read from the distribution database at a
time. The commit batch size controls how frequently these commands are
committed to the distribution database. The lower the number the more
frequent this occurs, the higher the less it occurs but more resources are
consumed. So these settings controls the chattiness of the log reader agent
back with the subsystem. You want some chattiness, but not too much as it
increases the over head; you want some of these transactions in ram, but
with this setting too high performance is degraded. You will have to tune
this for your environment.
--
Hilary Cotter
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

[quoted text, click to view]