Regards

BACKUP LOG [GBKSMART] TO DISK = N’C:\Backup\DBName_log.bak’

–**** Shrinking Database

–USE [DBName];
GO
– Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE DBName
SET RECOVERY SIMPLE;
GO
– Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE (DBName_Log, 1);
GO
– Reset the database recovery model.
ALTER DATABASE DBName
SET RECOVERY FULL;
GO

Thank You.

Msg 155, Level 15, State 1, Line 1
‘TRUNCATE_ONLY’ is not a recognized BACKUP option.

Then I used the second query. It works fine for me.
Thanks a lot

I had a bit of an issue with a new SQL 2012 setup, it somehow managed to get the Log files set to minimum size of 12GB… not sure how, I used the below to shrink it down (After backing up the Database of course)

USE
GO
DBCC SHRINKFILE(_log, 1)
BACKUP LOG to disk =’nul’
DBCC SHRINKFILE(_log, 1)
GO

So now the log files are initial size of 1mb again, my question is… do you have any ideas on how it might of got the initial size to be so large? My understanding of this value is it should remain at what you set it to, & when you backup the log files, shrink back down to this size.

For reference this is a 5GB Database with only minimal changes per day.

ALTER DATABASE ExampleDB SET RECOVERY SIMPLE
DBCC SHRINKFILE(‘ExampleDB_log’, 0, TRUNCATEONLY)
ALTER DATABASE ExampleDB SET RECOVERY FULL

So I went to your next suggestion of “BACKUP LOG [TestDb] TO DISK = N’C:\Backup\TestDb.bak’” and tried that with our scenario. Unfortunately, the log file backup that gets created is ~27k-40k in size, this coming from a 97gig log file. That cannot be right. And the 97 gig log file does not shrink down at all.

Am I missing something?

I read Brent Ozar’, and Paul Randel’ sections as you suggested. In my opinion, the weren’t as cut & dry as yours was, although I’m a big fan of Brent Ozar & have watched many of his videos.
Not sure what to at this point. My backups, despite being done daily, do not seem to be shrinking log files down to a manageable size & the SHRINKFILE comes into play with me more often then I am comfortable with.

Thank you for your time.

Question:
How do truncate the log ( as we take full back every day during Night)
How to Free the unused space in the data file.

Please advice, Thanks in advance.

Unable to increase the log file size and not apossbile to set to unrestricted for the same.

Thanks,
Jagan

the data files were placed on different drives which were running out of space. after executing truncate table commands. The database is showing lot of space that can be freed (off coarse). But we are unable to Shrink database. It either takes too long or gives timeout.

What is the quickest way ?

Shrinking a log file to a specified target size
The following example shrinks the log file in the AdventureWorks2008R2 database to 1 MB. To allow the DBCC SHRINKFILE command to shrink the file, the file is first truncated by setting the database recovery model to SIMPLE.

Transact-SQLCopy
USE AdventureWorks2008R2;
GO
– Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE AdventureWorks2008R2
SET RECOVERY SIMPLE;
GO
– Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE (AdventureWorks2008R2_Log, 1);
GO
– Reset the database recovery model.
ALTER DATABASE AdventureWorks2008R2
SET RECOVERY FULL;
GO

My database is in FULL recovery and can not change it to simple because i m using sharepoint 2010 database and simple mode is not support in production.

for that i took log full back.
truncate_only is not supported at SQL Server 2008. so i shrink file using management studio interface when i select log file and click to shrink screen close quickly without giving any error or message. and files does not shrink and its size is still same. please tell how to shrink file and get drive space back. thx.

Can you please help me. I want to use check point with my job, actually when my job run CPU takes 90-96 % usages which is not good, So please suggest what is the best solution to resolve this issue, so that the job not take a huge CPU usages.

Regards,
Sunil Kumar Kaushal

due to low disk space , i didn’t configure log backup. But Database is in full recovery model. For this reason log file size goes huge every week. Shall I shrink log file weekly once.. OR What i Want to do before shrnk the log file. If i shrink log file weekly once will it make physical fragmentation?

As i am going through the space issue in my server and my database has a grown bigger so i had deleted some tables from the database which were not necessary .now i have 6 gb unallocated space availlable in my db i shrink the db and my db recovered around 4 gb spaces as after doing R&D in my db i came to know that my 2 gb spaces is been occupied by the log file .
as my platform is sql server 2008 i can’nt truncate the logfile but as i am taking regular log_backup every 1 min.i want to make space free of log file.kindly suggest how to recover the 2 gb space or what to do.

backup log x to disk = ‘nul:’ –with truncate_onlyto disk = ‘nul:’

dbcc shrinkfile(x_log,1)