Distribution table cleanup

Using SQL Server 2005. Replication working fine except the distribution table is continuely growing. Started to configure maintenance job (catagory: REPL-Distribution Cleanup) Any suggested steps that will not break the replication. Is there a SP available that will address my problem.

Thanks,

You can reduce the retention period using sp_changedistributiondb.

For more info, please refer to the following articles.

http://msdn2.microsoft.com/fr-fr/library/ms146868.aspx

http://msdn2.microsoft.com/fr-fr/library/ms181877.aspx

Regards,

Gary

Distribution table cleanup

Using SQL Server 2005. Replication working fine except the distribution table is continuely growing. Started to configure maintenance job (catagory: REPL-Distribution Cleanup) Any suggested steps that will not break the replication. Is there a SP available that will address my problem.

Thanks,

You can reduce the retention period using sp_changedistributiondb.

For more info, please refer to the following articles.

http://msdn2.microsoft.com/fr-fr/library/ms146868.aspx

http://msdn2.microsoft.com/fr-fr/library/ms181877.aspx

Regards,

Gary

Distribution database is growing large...

Hi!
A few days ago the number of replication commands grew up to ~6 000
000. A normal number used to be ~20 000. The replication agents are
working fine. The data on subscribers are valid. I suspect that the
history clean up agents don't remove old commands, although their
status shows successful completion.
What could be a workout for such situation?
Thanks.
P.S.: I am using Win 2003 Ent Server + MS SQL 2000 sp3 and only
transactional replication.
Do you have anonymous subscriptions? If so the commands and transactions
will remain there until the end of the retention period.
Also it could be that you merely issued transactions that affected a large
number of rows. However, if these commands have been replicated to all
subscribers the distribution clean up agent should purge them every 10
minutes.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0412020529.372a7316@.posting.google.c om...
> Hi!
> A few days ago the number of replication commands grew up to ~6 000
> 000. A normal number used to be ~20 000. The replication agents are
> working fine. The data on subscribers are valid. I suspect that the
> history clean up agents don't remove old commands, although their
> status shows successful completion.
> What could be a workout for such situation?
> Thanks.
> P.S.: I am using Win 2003 Ent Server + MS SQL 2000 sp3 and only
> transactional replication.