Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a database in SQL Server 2005 whose transaction log becomes full. It is using snapshot replication. I noticed the transaction log is not freeing up space. So I created an additional transaction log. Three days has passed and this first transaction log is still full. I performed a full database backup and transaction backup. Then I tried to shrink the transaction log but the shrink failed.

Can anyone advise why shrinking transaction log is failing? ANy other recommendation on how to resolve the problem?

share|improve this question
Could you add some information about the error received with the transaction log fails? It's impossible to troubleshoot an error without the error details... – Scott Lundberg Mar 9 '10 at 15:31
Is this a first occurrence after a period of normal operation? If so, have there been any recent configuration changes? Is this a brand new set up? All bit of a follow-on to what Scott posted. – jl. Mar 9 '10 at 15:52 - good explanation including help (commands to analyze etc.)

;) have fun. Seriously - you need to do some analysis now.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.