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

I have some sql server database for which recovery model is set to full.Now for some databases the ldf size has become large.I tried taking log backup regularly,but i didn’t find decrease in physical size of ldf. I followed what stan20 has told in this link http://social.msdn.microsoft.com/Forums/en-US/databasedesign/thread/704bcfbc-9251-4f4e-9a80-04bc7fe9ae78 But it only reduced logical file size. So how i can mange size of ldf file?

marked as duplicate by Mark Storey-Smith, Jon Seigel, Aaron Bertrand, Leigh Riffel, ypercubeᵀᴹ Jan 14 '13 at 14:39

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.

migrated from stackoverflow.com Jan 13 '13 at 19:37

This question came from our site for professional and enthusiast programmers.

  • 2
    "I tried taking log backup regularly" - when you say 'tried' what do you mean? You either have a scheduled TLOg backup or you don't? – Mitch Wheat Jan 12 '13 at 12:01
  • I have done scheduled transaction backup – wincoding Jan 12 '13 at 12:13
  • 1

Backing up the transaction log will not shrink the physical file. It will only mark transactions as inactive and potentially mark virtual log file(s) for reuse. What you're looking to do is actually shrink the file system file, and this can be done through DBCC SHRINKFILE.

Note: shrinking the transaction log, or any other database file for that matter, should not be a routine database task. Proper sizing will mitigate the necessity for tasks like this.

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