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.

     

  • Run

    SELECT min_distretention, max_distRetention, History_Retention

    FROM msdb.dbo.MSdistributiondbs

    This will tell you the imte in hours that the distribution will hold replicated /non replicated data. If it is too hi for you, try putting a lower value.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply