What are the challenges you face when working across database platforms? Take the survey

After Transaction log backup ldf file is still huge

klasuyklasuy Posts: 3
edited January 9, 2015 5:25AM in SQL Backup Previous Versions

I'm wondering what i'm doing wrong.

My Intranet database it's log file keeps groing over time. It's allready 100Gb now. (the mdf file is 52Gb)
The database it's recovery model is in FULL mode.

We do a full backup every day at 6.30 and 23u.
We do transaction log backups every 15minutes.

For what i can read online a log file should automatic shrink when there is a transaction backup.
I our case this does not happen.

What info do you need more to help me on this issue?


  • Options

    SQL Server (and hence also SQL Backup) won't automatically shrink files, even though the space is freed up within the file by a log backup. You can manually shrink your log using DBCC SHRINKFILE (http://msdn.microsoft.com/en-us/library/ms189493.aspx), but you should only do this if it's unlikely to grow again in the future.

    In an ideal world, your log file will be large enough that it never normally has to auto-grow between log backups, as that will lead to poor performance. The "Best Practices" section of the MSDN article has some sensible advice.

    Hope that helps,
    Robert Chipperfield
    Red Gate
  • Options

    I have released the free space, that was 99%. Now the file is 1Gb and it's been like that for 2hours now.
Sign In or Register to comment.