Hello Everyone: I am a DBA. And, having issues with Transaction Log not shrinking. My user db that has issues, is with Full recovery model and I have full, dif and log backups running on schedule for it. It won't let me manually shrink the transaction log either. We are on SQL Server 2008 R2, what do I need to do to manage these transaction logs so that they shrink to an minimum size. Thank you for your feedback in advance!
First check that you don't have CDC enabled (Change Data Capture uses the log reader just like replication). Then double check that replication isn't happening. If you are 100% sure you are good then you can run [sp_removedbreplication] to get rid of replication on that database. That should clear things up allowing you to get that (extremely) large transaction backup job done allowing you to shrink the log. :
Before you go and start shrinking the transaction log I would ask as to why you are going to shrink it. It will just grow again, causing a performance hit, and you'll be right back where you started. If you truly want to shrink it, take a look at sys.databases and see what the log_reuse_desc value is. If you are waiting for replication or a log backup then you won't be able to perform the shrink. Perform a couple of log backups and then try to shrink the log by a small amount (it would be useful to know what command you are using for the shrink). Another alternative is to find a nice quiet period for your system and alter the recovery model to simple, shrink the log, and then put it back to full followed by a full or differential backup. All in all though I wouldn't shrink the log unless it's absolutely necessary.