Possible Duplicate:
Why Does the Transaction Log Keep Growing or Run Out of Space?

I am having trouble with my database, the log files is currently 250GB in size, I need to shrink this down somehow.

I have tried backing up the transactional log files, performing a full backup, running various shrink scripts but to no avail.

What are the correct steps to make this happen?

Can I somehow just truncate the whole log file then perform a full backup?

Thank You, Paul

marked as duplicate by Jack Douglas Dec 11 '12 at 16:17

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Not much to work on here. Can you detail the scripts you've run along with the output/observations? Also run this and add the output to your question. – Mark Storey-Smith Dec 8 '11 at 23:03
  • 1
    Run DBCC OPENTRAN and see if there are any open transactions that are holding onto the log file. – Eric Humphrey - lotsahelp Dec 9 '11 at 14:43

Do you need point it time recovery? If not then change the database's recovery model to Simple.

Does the database have mirroring or replication configured? That can also cause the transaction log to blow up quite large.

  • 2
    You can find the exact reason for the log not reusing space with SELECT name, log_reuse_wait_desc FROM sys.databases on 2005 or higher. This will give you a value you can lookup from msdn.microsoft.com/en-us/library/ms345414.aspx for how to resolve the problem. One note is that REPLICATION could mean Change Data Capture since it uses the Replication Log reader for data collection. – Jonathan Kehayias Dec 10 '11 at 0:18

Paul Randal has a good post on this topic: http://sqlskills.com/BLOGS/PAUL/post/Search-Engine-QA-1-Running-out-of-transaction-log-space.aspx

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