"matt" <matt@happytreefriends.com> wrote in message
news:320FB135-920D-4215-A019-826DE51140A1@microsoft.com...
> Have been assigned to fix this problem for a client.
>
> Basically the logreader is reading transactions at approx 500 cmd/sec and

"Hilary Cotter" wrote:

> what are the indexes like on the subscriber tables? You should minimize them
> as much as possible for maximum performance. Also do any triggers exist
> here?
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
>
> "matt" <matt@happytreefriends.com> wrote in message
> news:320FB135-920D-4215-A019-826DE51140A1@microsoft.com...
> > Have been assigned to fix this problem for a client.
> >
> > Basically the logreader is reading transactions at approx 500 cmd/sec and
> the distribution agent is on distibuting 8 -15 cmd/sec leaving thousands of
> transactions to process overnight... even delayad til the weekend. How do i
> speed up distribution agent. I have starting trying indexs on the large
> tables (that where missing from replication DB) however this is having
> minmal impact? ANY suggestions?
>
>