InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 08:47:38 GMT20http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxPlease run the following script to check why log entries are not removed:[code="sql"]select name, log_reuse_wait, log_reuse_wait_desc from sys.databaseswhere name = 'Distribution'[/code]Also run:[code="sql"]dbcc opentran()[/code]Wed, 26 Sep 2012 06:06:32 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxSimple recovery model.when the job 'Agent history clean up: distribution’ is executing the log file is growing rapidly.so i disabled the job for now.will it effect the replication ??up to what extents.Tue, 25 Sep 2012 12:38:37 GMTtapaskumardmhttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxWhat is the recovery model of your Distribution database? It is supposed to be "Simple". If it is something else, change it to Simple.Tue, 25 Sep 2012 11:16:31 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxI have the same Issue. I did all the above steps,but when I run the Job 'Agent history clean up : Distribution' .. the log file is growing rapidly.What can be done to resolve the issue.Thanks in advancedTue, 25 Sep 2012 07:29:59 GMTdm_tapashttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxTry this link, I believe it describes your problem.http://www.mssqltips.com/tip.asp?tip=1823Mon, 11 Jan 2010 16:47:56 GMTthatguyivanhttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxNext time it runs, it should clean up everything. But it will take time to run the clean up Job. I think you should try to run the clean up job manually. Just copy the command from the Job step and run it through SSMS. But that will not make the DB size small. But the latency will drop down to a manageable level.Fri, 27 Nov 2009 05:00:26 GMTRoy Ernesthttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxNext time it runs, it should clean up everything. But it will take time to run the clean up Job. I think you should try to run the clean up job manually. Just copy the command from the Job step and run it through SSMS. But that will not make the DB size small. But the latency will drop down to a manageable level.Fri, 27 Nov 2009 05:00:25 GMTRoy Ernesthttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspx[quote][b]Roy Ernest (11/26/2009)[/b][hr]The only thing that could keep it big then is that there are some commands that are that has not been replicated yet. What is your retention period?[/quote]Hi Roy,Thanks for your reply.For many of the publications, retention period was "subscription never expires". Just now I changed it to 72 hrs.msrepl_transactions table has 13 million rows and msrepl_commands table has 31 million rows.There are 51 rows in msrepl_transactions with entry_time older than 2009-06-07. Oldest is 2006-06-26 Will changed retention period fix the issue?Regards,SureshFri, 27 Nov 2009 02:58:14 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxThe only thing that could keep it big then is that there are some commands that are that has not been replicated yet. What is your retention period?Thu, 26 Nov 2009 06:03:32 GMTRoy Ernesthttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspx[quote][b]Roy Ernest (11/25/2009)[/b][hr]Is it failing? The distribution agent clean up Job?Try running the the clean up job from the SSMS under your Account and see if it is giving any error or warnings[/quote]No. It is not failing.Distribution agent clean up job is taking more than 2 hrs to complete. It is scheduled to run every 10 minutes.Thu, 26 Nov 2009 03:40:06 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxIs it failing? The distribution agent clean up Job?Try running the the clean up job from the SSMS under your Account and see if it is giving any error or warningsWed, 25 Nov 2009 07:44:11 GMTRoy Ernesthttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspx[quote][b]glugingboulder (11/24/2009)[/b][hr]Just a thought, its possible that the distribution clean up agent is running under a account which doesn’t have permissions or doesn’t exist anymore worth checking.Therefore isn’t cleaning up the distributed commands[/quote]Distribution clean up agent is running under the account which has all the permissions.Wed, 25 Nov 2009 06:35:54 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspx[quote][b]Ian Scarlett (11/25/2009)[/b][hr]Is it the distribution database itself, or the transaction log that is growing?If it's the transaction log, check the recovery model. If it's anything other than simple, you need to make sure you're running transaction log backups.[/quote]It is the database itself that is growing. Not transaction log.Recovery model is simple.Wed, 25 Nov 2009 06:33:17 GMTSuresh B.http://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxIs it the distribution database itself, or the transaction log that is growing?If it's the transaction log, check the recovery model. If it's anything other than simple, you need to make sure you're running transaction log backups.Wed, 25 Nov 2009 01:05:30 GMTIan Scarletthttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxJust a thought, its possible that the distribution clean up agent is running under a account which doesn’t have permissions or doesn’t exist anymore worth checking.Therefore isn’t cleaning up the distributed commandsTue, 24 Nov 2009 20:20:28 GMTglugingboulderhttp://www.sqlservercentral.com/Forums/Topic823649-291-1.aspxDistribution database is 28 GB and growing 1GB per day.I have changed the retention period from subscription never expires to 24 hrs as recommended in [url]http://www.mssqltips.com/tip.asp?tip=1823[/url]ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/542f0613-5817-42d0-b841-fb2c94010665.htmHowever, the distribution database is still growing.Why is it not working?Mon, 23 Nov 2009 22:35:34 GMTSuresh B.