|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
|
|
Distribution 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 http://www.mssqltips.com/tip.asp?tip=1823 ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/542f0613-5817-42d0-b841-fb2c94010665.htm
However, the distribution database is still growing. Why is it not working?
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Today @ 3:25 PM
Points: 55,
Visits: 418
|
|
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
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 8:44 AM
Points: 1,322,
Visits: 4,399
|
|
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.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
|
|
Ian Scarlett (11/25/2009) 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.
It is the database itself that is growing. Not transaction log. Recovery model is simple.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
|
|
glugingboulder (11/24/2009) 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
Distribution clean up agent is running under the account which has all the permissions.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Monday, May 13, 2013 8:24 AM
Points: 3,280,
Visits: 6,619
|
|
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
-Roy
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
|
|
Roy Ernest (11/25/2009) 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
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.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Monday, May 13, 2013 8:24 AM
Points: 3,280,
Visits: 6,619
|
|
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?
-Roy
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
|
|
Roy Ernest (11/26/2009) 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?
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,
Suresh
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Monday, May 13, 2013 8:24 AM
Points: 3,280,
Visits: 6,619
|
|
Next 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.
-Roy
|
|
|
|