Truncate Transaction Log in SQL Server 2008 - by Madhu K Nair

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 330211 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/27/2008 12:26:30 AM
Access Restriction Public


I have a database with the following size

SELECT name,size from sys.database_files

Test 173056
Test_Log 579072 -- 565 MB

Now I want to truncate Transaction log. In earlier version what we do is we truncate the log and shrink the file. 
Sign in to post a comment.
Posted by Microsoft on 2/27/2008 at 12:09 PM
Madhu, I saw that you used SQL Server 2008 July 2007 CTP. The latest CTP is SQL Server 2008 Feb 2008 CTP is more stable and please give it a try.

I'd like to gather more information:
- what information message shrink return when you could not shrink the file? Usually the information message would be very helpful hint for what shrink thinks.

- could you use 'DBCC LOGINFO' and give me the result of which log file is active?

I tried the latest CTP and have no problem to shrink the log file. However, I did not make any changes in shrink code (maybe log manager code has some change that I am unaware of, but it is highly unlikely). Is it possible to share out your database?


By the way, for SQL Server 2005, you have full recovery model. After log backup, shrink succeeded. This is not apple-to-apple comparison with SQL Server 2008 (simple recovery model and log backup is not available).