June 11, 2013 at 1:55 pm
Recently I encountered an issue where the transaction logs in my production databases have been growing up to 1 TB and I have not been able to shrink them. After some initial investigation I found that the log_reuse_wait_desc in sys.databases is REPLICATION for all databases in question. This made sense as these databases are set up for transactional replication. I then executed sp_repldone as many online resources suggest and that cleaned up the transaction log. However, the issue keeps resurfacing so running sp_repldone once a day is far from a permanent solution.
It is my understanding that the log reader agent is responsible for running sp_repldone on a regular basis. However, I do not see this happening when I run a profiler trace on the server. Does anyone know how the log reader agent calls sp_repldone or why it isn't running? Any insight would be appreciated.
Server - SQL Server 2008 R2 SP1 Enterprise Edition
June 11, 2013 at 4:37 pm
Is the log reader agent running? Are the replication publications working?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 12, 2013 at 8:53 am
Yeah, the log reader agent is running. I did try restarting it but that didn't help. Everything is syncing like it should keeping tables on the subscriber up to date.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply