OK so I've seen tons of information around about shrinking and free space and similar, but what I've not been able to see is just the basics for SQL Server 2008 on free space in the logfile.

I was under the impression (and this seems to be the case for previous versions of SQL Server) that when a full backup was done, then logs that had completed were freed up (i.e. if you had a 500MB log file with 10% free space before a full backup you might end up with 100MB log file with 70% free space after a full backup).

In SQL Server 2008 I have been checking the sizes (i've got about 10% free space), doing a backup (BACKUP DATABASE DBNAME TO DISK = 'C:\temp\DBNAME.bak') and then checking the sizes (no file size change, still about 10% free space) ... was expecting an increase in free space.

Am I doing my backup incorrect? Is this not the correct way to do this? What does one need to do to make this behave? Or does it just not behave this way anymore?

EDIT: Accepting Answer Below, Adding Script Items I Used

SELECT log_reuse_wait_desc, * FROM DBNAME.sys.databases WHERE name = 'DBNAME'
SELECT log_reuse_wait_desc, * FROM DBNAME.sys.databases WHERE name = 'DBNAME'


A backup does not automatically release the tx logs.


for a full backup sequence (kill the shrinkfile i oyou dont want that).


To stay here (on server fault) that question was answered under

SQL Server (2005/2008): Does full backup truncate the log in full recovery mode

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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