Comments on: Shrink the Unshrinkable SQL Transaction Log http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/ Take a byte out of tech! Wed, 08 Feb 2012 15:54:01 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: James http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-119042 James Tue, 06 Dec 2011 19:20:37 +0000 http://blog.crankybit.com/?p=309#comment-119042 Works nice,found it here too http://www.sqlserveroptimizer.com/2011/11/how-to-shrink-logfile-in-sql-server-20052008/ thanks again Works nice,found it here too

http://www.sqlserveroptimizer.com/2011/11/how-to-shrink-logfile-in-sql-server-20052008/

thanks again

]]> By: Mark Thornton http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-111706 Mark Thornton Wed, 05 Oct 2011 11:31:04 +0000 http://blog.crankybit.com/?p=309#comment-111706 Brilliant - you not only confirmed my suspicions of a bug in SQL Server 2008, but also gave me a workaround. Many thanks! Brilliant – you not only confirmed my suspicions of a bug in SQL Server 2008, but also gave me a workaround.

Many thanks!

]]> By: amith http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-109137 amith Wed, 14 Sep 2011 06:37:44 +0000 http://blog.crankybit.com/?p=309#comment-109137 " perfect solution " thanx a lot........ ” perfect solution ”

thanx a lot……..

]]> By: Dean http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-101293 Dean Mon, 11 Jul 2011 16:49:06 +0000 http://blog.crankybit.com/?p=309#comment-101293 Piecing the post and comments together, what worked for me in the end with SQL 2008 was the following: BACKUP LOG DatabaseName TO DISK = N'D:\Backup\DatabaseName_log.bak' GO DBCC SHRINKFILE("MyDatabase_Log", 1) GO Thanks guys. Piecing the post and comments together, what worked for me in the end with SQL 2008 was the following:

BACKUP LOG DatabaseName TO DISK = N’D:\Backup\DatabaseName_log.bak’
GO
DBCC SHRINKFILE(“MyDatabase_Log”, 1)
GO

Thanks guys.

]]> By: Tim http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-71489 Tim Tue, 18 Jan 2011 16:16:18 +0000 http://blog.crankybit.com/?p=309#comment-71489 Thanks! worked Thanks! worked

]]> By: Jim http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-71335 Jim Mon, 17 Jan 2011 20:32:09 +0000 http://blog.crankybit.com/?p=309#comment-71335 Brilliant. Bacon saved, thanks. Brilliant. Bacon saved, thanks.

]]> By: SQL Server 2005 can’t increase log file size Drija http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-61058 SQL Server 2005 can’t increase log file size Drija Thu, 18 Nov 2010 08:09:03 +0000 http://blog.crankybit.com/?p=309#comment-61058 [...] Found a solution. [...] [...] Found a solution. [...]

]]> By: Dave http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-46640 Dave Wed, 30 Jun 2010 14:12:04 +0000 http://blog.crankybit.com/?p=309#comment-46640 Good article on the issue of transaction log management: http://www.sqlskills.com/BLOGS/PAUL/post/Importance-of-proper-transaction-log-size-management.aspx Good article on the issue of transaction log management:

http://www.sqlskills.com/BLOGS/PAUL/post/Importance-of-proper-transaction-log-size-management.aspx

]]> By: Sonet http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-45585 Sonet Fri, 11 Jun 2010 00:06:33 +0000 http://blog.crankybit.com/?p=309#comment-45585 Why not simply backup the logs? TRUNCATE_ONLY has been removed for a reason. The problem with it is that it breaks the transaction log chain, which makes recovering to a point in time impossible. This should be avoided under all circumstances. Instead backup the database log: BACKUP LOG DatabaseName TO DISK = N'C:\Backup\DatabaseName_log.bak' GO If you are still running out of space, perform log backups more frequently. Why not simply backup the logs? TRUNCATE_ONLY has been removed for a reason. The problem with it is that it breaks the transaction log chain, which makes recovering to a point in time impossible. This should be avoided under all circumstances. Instead backup the database log:

BACKUP LOG DatabaseName TO DISK = N’C:\Backup\DatabaseName_log.bak’
GO

If you are still running out of space, perform log backups more frequently.

]]> By: Jason http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-42957 Jason Mon, 19 Apr 2010 16:33:29 +0000 http://blog.crankybit.com/?p=309#comment-42957 Obviously SQL 2008 disabled TRUNCATE_ONLY. Their workaround is to set Recovery Mode to Simple, do the DBCC SHRINKFILE, then set it back to Full. This does not make SQL Server more secure at all - it just creates more work for the DBA. What I want to know is, how to shrink that 37GB T-log file WITHOUT taking the database out of Full Recovery mode, and WITHOUT jeopardizing point-in-time restore. I have a 24/7 OLTP system with lots of transactions. The log file is going to grow and I don't have 2 TB of fast disk space to reserve for the logs. So I need to reduce it without losing Point-In-Time recovery. Any thoughts??? Obviously SQL 2008 disabled TRUNCATE_ONLY.
Their workaround is to set Recovery Mode to Simple, do the DBCC SHRINKFILE, then set it back to Full.
This does not make SQL Server more secure at all – it just creates more work for the DBA.

What I want to know is, how to shrink that 37GB T-log file WITHOUT taking the database out of Full Recovery mode, and WITHOUT jeopardizing point-in-time restore.
I have a 24/7 OLTP system with lots of transactions. The log file is going to grow and I don’t have 2 TB of fast disk space to reserve for the logs. So I need to reduce it without losing Point-In-Time recovery.

Any thoughts???

]]> By: Liz http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-36031 Liz Fri, 06 Nov 2009 15:00:13 +0000 http://blog.crankybit.com/?p=309#comment-36031 Thank you - that's brilliant. Thank you – that’s brilliant.

]]> By: Dallas http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-34067 Dallas Thu, 10 Sep 2009 03:21:01 +0000 http://blog.crankybit.com/?p=309#comment-34067 truncate_only is no longer supported in sql server 2008. See: http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d0958b81-8cfb-4b2b-8b5a-8e50c835f920 truncate_only is no longer supported in sql server 2008.
See:
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d0958b81-8cfb-4b2b-8b5a-8e50c835f920

]]> By: dude http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-33444 dude Thu, 20 Aug 2009 19:06:57 +0000 http://blog.crankybit.com/?p=309#comment-33444 Thanks! I just did this to a 80gb log file! everything's back to normal now :) Thanks! I just did this to a 80gb log file! everything’s back to normal now :)

]]> By: Rasesh http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-33240 Rasesh Fri, 14 Aug 2009 17:41:37 +0000 http://blog.crankybit.com/?p=309#comment-33240 THANK YOU SOOOOO MUCH!!! THANK YOU SOOOOO MUCH!!!

]]> By: rob http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-32611 rob Mon, 20 Jul 2009 21:10:45 +0000 http://blog.crankybit.com/?p=309#comment-32611 Dude, you are a genius. Thank you, thank you, thank you so much. Dude, you are a genius. Thank you, thank you, thank you so much.

]]> By: Praesagus http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-29673 Praesagus Tue, 12 May 2009 21:43:35 +0000 http://blog.crankybit.com/?p=309#comment-29673 You saved my life - thanks! You saved my life – thanks!

]]> By: Administrator http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-27595 Administrator Sat, 04 Apr 2009 01:29:49 +0000 http://blog.crankybit.com/?p=309#comment-27595 Juls, I corrected your original comment and deleted the comment pointing out the correction. Thanks. Juls, I corrected your original comment and deleted the comment pointing out the correction. Thanks.

]]> By: Juls Briosos http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-27561 Juls Briosos Fri, 03 Apr 2009 04:57:33 +0000 http://blog.crankybit.com/?p=309#comment-27561 we were having this same problem today and this same solution did the trick! we were breaking our necks trying to shrink the database logs to no avail... I sure wish we saw this post a little earlier.. :P Thanks!! we were having this same problem today and this same solution did the trick! we were breaking our necks trying to shrink the database logs to no avail… I sure wish we saw this post a little earlier.. :P Thanks!!

]]> By: Buba Rooni http://blog.crankybit.com/shrink-the-unshrinkable-sql-transaction-log/#comment-22838 Buba Rooni Tue, 11 Nov 2008 21:38:13 +0000 http://blog.crankybit.com/?p=309#comment-22838 Perfect! I've had a db that wouldn't post any transaction the last few days, nothing I tried would shrink it and I had management breathing fire down my neck. Your script did the trick! Thanks! Perfect! I’ve had a db that wouldn’t post any transaction the last few days, nothing I tried would shrink it and I had management breathing fire down my neck.

Your script did the trick!

Thanks!

]]>