SQL Server 2005 log size & replication issue
Posted on 2008-06-11
I have a problem that occur times to times. My transaction log are full and taking all disk space. The workaround we find is :
stop transaction log reader agent
run EXEC sp_repldone ...
restart transaction log reader agent
But this take some hours,
My question is What cause this appen and how to prevent is to occur in the future?
If I define 10 transaction log of 10Go each, is I'll be able to shrink some of them while other are locked?