"Richard S. Hale" wrote:

> There are several optimization techniques for transactional replication one
> half is to create a new distribution agent profile with a lower amount of
> transactions set per commit, and the second half is to add [-MaxCmdsInTran
> 10000] to the log reader agent where 10000 is the maximum number of commands
> per transaction. With this switch added to the execution command in the
> actual log reader agent you will only send 10000 commands down the
> replication pipe per transaction. The combination of these two performance
> enhancements will reduce that 8 hour run to quite a bit smaller. :)
>
> "BSandia" wrote:
>
> > I have a publication that is being pulled and when I execute a UPDATE command
> > example: UPDATE Oils SET Description = 'This is a description'
> >
> > The SQL Query Analyzer completes the command successfully.
> > I am receiving confirmation that more than 30,0000 rows have been updated
> > when I run this command.
> >
> > When I go to the Replication Manager and view the Subscription it continues
> > to run indefinitely.
> >
> > In some cases more than 8 hrs.
> >
> > Are there some parameters that might need to be set when running this
> > process?
> >
> > Any feedback is appreciated.
> >
> > Thank you
> >
> >
> >
> >