Comments on: SQL SERVER – Shrinking Truncate Log File – Log Full http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/ Notes of a SQL Server MVP and Database Administrator Fri, 20 Nov 2009 20:17:18 +0000 http://wordpress.com/ hourly 1 By: Nilesh http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57650 Nilesh Mon, 16 Nov 2009 18:48:24 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57650 Ritesh, The 'quote' did not help. Same error. Baffled now !! -------------------------------------- why don’t you try this one? USE 8PSTDB GO DBCC SHRINKFILE(‘8PSTDB_log’, 1) BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY DBCC SHRINKFILE(‘8PSTDB_log’, 1) GO BTW, it is not a good idea to truncate log manually rather do take backup of your database regularly and also take backup of your log files after every few hours, depends on your risk handling capacity. Ritesh,

The ‘quote’ did not help. Same error. Baffled now !!

————————————–
why don’t you try this one?

USE 8PSTDB
GO
DBCC SHRINKFILE(‘8PSTDB_log’, 1)
BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY
DBCC SHRINKFILE(‘8PSTDB_log’, 1)
GO

BTW, it is not a good idea to truncate log manually rather do take backup of your database regularly and also take backup of your log files after every few hours, depends on your risk handling capacity.

]]> By: Imran Mohammed http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57617 Imran Mohammed Sun, 15 Nov 2009 05:44:15 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57617 @Rakesh, Can you please post your email id here, I have a script, with does exactly what you asked for. please leave your email id, write it in the post, so that it is visible to me and I will have it emailed. ~ IM. @Rakesh,

Can you please post your email id here,

I have a script, with does exactly what you asked for.

please leave your email id, write it in the post, so that it is visible to me and I will have it emailed.

~ IM.

]]> By: Ritesh Shah http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57616 Ritesh Shah Sun, 15 Nov 2009 04:18:55 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57616 Hi Rakesh, this is possible for sure but I don't recommend to truncate transaction log manually, even if you would like to do it, please refer below given link. h ttp://www.sqlhub.com/2009/05/shrink-log-file-for-all-database-in-sql.html Hi Rakesh,

this is possible for sure but I don’t recommend to truncate transaction log manually, even if you would like to do it, please refer below given link.

h ttp://www.sqlhub.com/2009/05/shrink-log-file-for-all-database-in-sql.html

]]> By: Rakesh http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57614 Rakesh Sat, 14 Nov 2009 22:21:52 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57614 Is there a way to shrink all log files for many SQL databases in one go for SQL2005 and SQL2000, as I would a like script for this, for SQL2000 and SQL2005 Thanks Is there a way to shrink all log files for many SQL databases in one go for SQL2005 and SQL2000, as I would a like script for this, for SQL2000 and SQL2005

Thanks

]]> By: Ritesh Shah http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57583 Ritesh Shah Fri, 13 Nov 2009 06:28:31 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57583 Nilesh, why don't you try this one? USE 8PSTDB GO DBCC SHRINKFILE('8PSTDB_log', 1) BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY DBCC SHRINKFILE('8PSTDB_log', 1) GO BTW, it is not a good idea to truncate log manually rather do take backup of your database regularly and also take backup of your log files after every few hours, depends on your risk handling capacity. Nilesh,

why don’t you try this one?

USE 8PSTDB
GO
DBCC SHRINKFILE(‘8PSTDB_log’, 1)
BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY
DBCC SHRINKFILE(‘8PSTDB_log’, 1)
GO

BTW, it is not a good idea to truncate log manually rather do take backup of your database regularly and also take backup of your log files after every few hours, depends on your risk handling capacity.

]]> By: nilesh http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57567 nilesh Fri, 13 Nov 2009 00:21:46 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57567 in case the above error message is misleading, I copy pasted the error message from another db which starts with 8RINKS - which also throws an error same as the 8PSTDB in case the above error message is misleading, I copy pasted the error message from another db which starts with 8RINKS – which also throws an error same as the 8PSTDB

]]> By: nilesh http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-57566 nilesh Fri, 13 Nov 2009 00:18:34 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-57566 This script worked for all my databases, but any database that starts with a number, I get error. any help appreciated. thanks USE 8PSTDB GO DBCC SHRINKFILE(8PSTDB_log, 1) BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY DBCC SHRINKFILE(8PSTDB_log, 1) GO ------------------------ Error message ------------------------- Msg 102, Level 15, State 1, Line 1 Incorrect syntax near '8'. Msg 102, Level 15, State 1, Line 1 Incorrect syntax near 'rinks_log'. Msg 319, Level 15, State 1, Line 2 Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. Msg 102, Level 15, State 1, Line 3 Incorrect syntax near 'rinks_log'. This script worked for all my databases, but any database that starts with a number, I get error. any help appreciated. thanks

USE 8PSTDB
GO
DBCC SHRINKFILE(8PSTDB_log, 1)
BACKUP LOG 8PSTDB WITH TRUNCATE_ONLY
DBCC SHRINKFILE(8PSTDB_log, 1)
GO

————————
Error message
————————-
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near ‘8′.
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near ‘rinks_log’.
Msg 319, Level 15, State 1, Line 2
Incorrect syntax near the keyword ‘with’. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.
Msg 102, Level 15, State 1, Line 3
Incorrect syntax near ‘rinks_log’.

]]> By: Ravinder http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-56553 Ravinder Fri, 09 Oct 2009 07:37:56 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-56553 Thanks for the above code, it worked. Thanks for the above code,
it worked.

]]> By: Lars Mikkelsen http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55908 Lars Mikkelsen Wed, 16 Sep 2009 07:30:56 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55908 John: Try USE [SharePoint_AdminContent_065b8fa2-f141-42ab-8b82-7b8bf659f7c2] Some database names needs to have surrounding brackets. John: Try USE [SharePoint_AdminContent_065b8fa2-f141-42ab-8b82-7b8bf659f7c2]

Some database names needs to have surrounding brackets.

]]> By: Ramanathan http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55739 Ramanathan Wed, 09 Sep 2009 06:21:32 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55739 I work with SQL 2000. I use the follwoing script for reducing the log file size. There is no need of "use (database)" command dbcc shrinkdatabase (powerbrain) go backup log powerbrain with truncate_only go I use shrinkdatabase instead of shrinkfile where you may need to use "use database" command. I used to run this script in query analyser. I work with SQL 2000.

I use the follwoing script for reducing the log file size.
There is no need of “use (database)” command

dbcc shrinkdatabase (powerbrain)
go
backup log powerbrain with truncate_only
go

I use shrinkdatabase instead of shrinkfile where you may need to use “use database” command. I used to run this script in query analyser.

]]> By: Justin Biggs http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55559 Justin Biggs Thu, 03 Sep 2009 12:43:51 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55559 @Hans I've seen the issue with the shrink command not working from management studio before. In my case, the logical file names on the .mdf and .ldf didn't match the name of the database. Fixing this seemed to allow the shrink commands to work. @Hans

I’ve seen the issue with the shrink command not working from management studio before. In my case, the logical file names on the .mdf and .ldf didn’t match the name of the database. Fixing this seemed to allow the shrink commands to work.

]]> By: John http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55527 John Wed, 02 Sep 2009 13:57:46 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55527 I misread the error message but still seek knowledge. It does not like the dashes...but I am not a DBA(this just fell into my lap and now I have to fix it) and not familiar with what my options are at this point. I misread the error message but still seek knowledge. It does not like the dashes…but I am not a DBA(this just fell into my lap and now I have to fix it) and not familiar with what my options are at this point.

]]> By: John http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55524 John Wed, 02 Sep 2009 13:29:12 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55524 I found this post very helpful but ran into an issue when using this against a Sharepoint database. Full DB Name below: USE SharePoint_AdminContent_065b8fa2-f141-42ab-8b82-7b8bf659f7c2 The error message that I get is listed below: Could not locate entry in sysdatabases for database 'SharePoint_AdminContent_065b8fa2'. No entry found with that name. Make sure that the name is entered correctly. It looks like it is Stopping after 32 characters. Is there something else I must specify to allow it to use more than 32 characters? I found this post very helpful but ran into an issue when using this against a Sharepoint database. Full DB Name below:

USE SharePoint_AdminContent_065b8fa2-f141-42ab-8b82-7b8bf659f7c2

The error message that I get is listed below:

Could not locate entry in sysdatabases for database ‘SharePoint_AdminContent_065b8fa2′. No entry found with that name. Make sure that the name is entered correctly.

It looks like it is Stopping after 32 characters. Is there something else I must specify to allow it to use more than 32 characters?

]]> By: Hans Groenewege http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55500 Hans Groenewege Wed, 02 Sep 2009 04:58:13 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55500 I am using the newest Microsoft SQL Version 8. Guess what, the shrinkage methods in SQL SERVER MANAGEMENT STUDIO are not working or make hardly a dent in the Log file size. Also the log files grow much faster than the actual databases. The method I used to shrink the log files is the one described here by Praveen Barath and which involves detaching the database in question, renaming the logfile, attaching the database again but now removing the log file and after DB data verification deleting the log file completely. I have no idea why the shrinkage utilities within management studio are not working at all. Thanks for the tip an keep up the good work. I am using the newest Microsoft SQL Version 8. Guess what, the shrinkage methods in SQL SERVER MANAGEMENT STUDIO are not working or make hardly a dent in the Log file size. Also the log files grow much faster than the actual databases.

The method I used to shrink the log files is the one described here by Praveen Barath and which involves detaching the database in question, renaming the logfile, attaching the database again but now removing the log file and after DB data verification deleting the log file completely.
I have no idea why the shrinkage utilities within management studio are not working at all.

Thanks for the tip an keep up the good work.

]]> By: Arks http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-55166 Arks Mon, 24 Aug 2009 19:49:25 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-55166 Hi, My database (sql 2005) is only full recovery mode. The transaction log grew way too big about 34GB. So, what I did was 1. shrink file using dbcc shrink file 2. backed up the transaction log using to a file 3. Issue DBCC shrink file Now here is my question, I know if I use the truncate only option on step2 and shrink the file, it will reduce the log file size. But If I do this I am seeing messages on event viewer saying "BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log." Since, I have backed up the log file in step2 to a file, Can I safely truncate the log file? If so Will I be able to recover to a point in time? Hi,
My database (sql 2005) is only full recovery mode. The transaction log grew way too big about 34GB. So, what I did was
1. shrink file using dbcc shrink file
2. backed up the transaction log using to a file
3. Issue DBCC shrink file

Now here is my question, I know if I use the truncate only option on step2 and shrink the file, it will reduce the log file size. But If I do this I am seeing messages on event viewer saying

“BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple
recovery model should be used to automatically truncate the transaction log.”

Since, I have backed up the log file in step2 to a file, Can I safely truncate the log file? If so Will I be able to recover to a point in time?

]]> By: raghu http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-54808 raghu Thu, 13 Aug 2009 06:35:32 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-54808 hi Pinal, i have experienced that SHRINK DB causes fragmentation... do TEMP DB grow for SHRINK DB ?? hi Pinal,

i have experienced that SHRINK DB causes fragmentation… do TEMP DB grow for SHRINK DB ??

]]> By: Babu http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-53811 Babu Sat, 18 Jul 2009 02:32:40 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-53811 Dear Pinal Dev, This is the first time i'm coming to this forum. It is very useful. Imran Mohd also doing wonderful job. He is giving info in depth Dear Pinal Dev,

This is the first time i’m coming to this forum. It is very useful. Imran Mohd also doing wonderful job. He is giving info in depth

]]> By: Uday http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-53761 Uday Thu, 16 Jul 2009 12:29:34 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-53761 Hi Pinal, My database (replication with one more server) has grown to the hard disk limit, I tired using the above script, it threw an error, secondly when I take the backup the .bak file size is same as data + Log file size. Please suggest. Hi Pinal,

My database (replication with one more server) has grown to the hard disk limit, I tired using the above script, it threw an error, secondly when I take the backup the .bak file size is same as data + Log file size. Please suggest.

]]> By: Roger http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-53678 Roger Tue, 14 Jul 2009 04:18:11 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-53678 Pinal, You are great. Thanks again, this is very very helpful. Pinal,

You are great. Thanks again, this is very very helpful.

]]> By: pinaldave http://blog.sqlauthority.com/2006/12/30/sql-server-shrinking-truncate-log-file-log-full/#comment-53560 pinaldave Thu, 09 Jul 2009 04:18:34 +0000 http://blog.sqlauthority.com/2006/12/30/shrinking-truncated-log-file/#comment-53560 @Paul Randal, Thank you for your comment Sir, I very much agree with you. I was only 60 days in blogging and SQL Server when I wrote this post and at that time I was even working with SQL Server 2000. Again, thanks for your coming here to help community who are reading this. Kind Regards, Pinal @Paul Randal,

Thank you for your comment Sir, I very much agree with you.

I was only 60 days in blogging and SQL Server when I wrote this post and at that time I was even working with SQL Server 2000.

Again, thanks for your coming here to help community who are reading this.

Kind Regards,
Pinal

]]>