How to resolve when Distribution Database is growing huge (+25gig)

re: How to resolve when Distribution Database is growing huge (+25gig)

Chetan Jain — Wed, 28 Dec 2011 06:03:30 GMT

We used this technique over many servers and it has worked perfectly fine for us! Thanks for sharing this.

I have one question through, we have a very large 630 G dist database. We are unable to perform cleanup on this even after above suggestions have been implemented. Do u have any other suggestions? the problem is we are cannot stop the distribution jobs for some time as the replication is critical. is there any way without stopping the distribution jobs.

name,rows,reserved,data,index_size,unused

MSrepl_commands,1498027110 ,616052376 KB,610869472 KB,5047928 KB,134976 KB

name,rows,reserved,data,index_size,unused

MSrepl_transactions,265722520 ,16021656 KB,15858120 KB,116216 KB,47320 KB

re: How to resolve when Distribution Database is growing huge (+25gig)

Raman Gosala — Tue, 24 Aug 2010 16:38:48 GMT

Chris,

Wonderful comments on the internal procs the default job was kinds very slow process and your steps was a flush out.

very impressive

Thanks again

Raman Gosala

re: How to resolve when Distribution Database is growing huge (+25gig)

Suresh — Thu, 04 Feb 2010 12:39:20 GMT

There is already a job called "Distribution clean up: distribution" to execute the query given in step 8.