July 14, 2009 at 8:46 am
Hello room,
I setup Pull transaction replication between MS SQL Server 2008 and MS SQL Server 2000.
•SQL Server 2008 (a subscriber)
•SQL Server 2008 (a remote distributor)
•SQL Server 2000 (Publishers)
in non trusted environment.
Recently, the applications acted sluggish and some developers complained the MS SQL Server 2000 (Publishers) logs grow tremendously due to database replications.
Note: The MS SQL Server 2000 (Publisher) is setup with Simple Recovery Model.
Questions: Can transaction replication cause/effect MS SQL Server 2000’s logs to grow (tremendous)?
Thanks in advance.
Edwin
July 14, 2009 at 8:54 am
Edwin (7/14/2009)
Questions: Can transaction replication cause/effect MS SQL Server 2000’s logs to grow (tremendous)?
This can happen if your log reader agent is not running OR coz of any issue is unable to read transaction log of the publisher and bringing the changes to the distributer. In either case, checkpoint will not cause the log to be truncated and hence it can grow.
Same applies if your publisher is in FUll recovery mode, here too backup log wont truncate the tran logs until the transactions have been read by the log reader agent.
July 14, 2009 at 9:10 am
Thanks for F.Y.I.
Sometimes the network lines down for two days on the Publisher's site, and sometimes the firewall issues.
Then, the log reader agent won't able to comm with Publishers.
Could this cause the problems?
July 14, 2009 at 9:17 am
Yes this could be a possible reason. Since transactions are not read by the logread.exe, logs on publisher wont be truncated and will continue to grow.
July 14, 2009 at 9:41 am
Thanks again. Your inside and clarifications answered my questions. 🙂
July 14, 2009 at 9:44 am
Thanks for the feedback 🙂
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply