June 24, 2008 at 3:34 am
Hi All
Please assist, my sql log reader once got full and no transactions could be processed nor shrinking, truncating the log file. So i had to do a differential backup of the database and deleted unnecessary files from disk where the log file is and i also have a job that backups the log every 2 hours. i reconfigured Replication Log Reader with a new profile having a longer timeout period.
Can someone advise what caused Replication Log Reader to timeout while it was working okay since our sql upgrade.
Thanks
New SQL DBA
It's better to fail while trying, rather than fail without trying!!!
June 24, 2008 at 11:44 am
Is there any error message for Log Reader?
July 20, 2011 at 5:36 am
HI,,
there is a question i would like to pose. How safe is it to start and stop log reader agent in transactional replication 2008 when transaction log in publication database writes records to be published ? is there any danger to lose changes that must be replicated ?
July 28, 2011 at 10:23 am
Check your Distribution db size. It could be that your retention for the Distribution agent is ridiculously high therefore cleanup tasks and log backups take longer therefore Log Reader gets locked and times out.
To view it right click on Replication Monitor and Distributor Properties and then properties. Stab in the dark but the most obvious answer I can give off the info provided 🙂
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply