-
Title
Backup transaction log with option TRUNCATE_ONLY does not create backup file -
Description
When using LiteSpeed Database Backup Wizard, advanced option to backup TRUNCATE_ONLY, no backup file is being created.
The script generated is: /* no_translate */ backup log [DatabaseName] WITH TRUNCATE_ONLY /* end_no_translate */ -
Resolution
The option TRUNCATE_ONLY will not backup any log.The purposeis to only truncate the inactive part of the log without making a backup copy. The function is the sameusing LiteSpeed GUI or native SQL Server tools.LiteSpeed may generate an informational message similar to:
Setting database option RECOVERY to SIMPLE for database [database name]
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log. -
Additional Information
For additional information, seehttp://msdn2.microsoft.com/en-US/library/aa933082(SQL.80).aspxAUTO_SHRINK only reduces the size of the transaction log if the database is set to SIMPLE recovery model or if the log is backed up.The AUTO_SHRINK option causes files to be shrunk when more than 25 percent of the file contains unused space. The file is shrunk to a size where 25 percent of the file is unused space, or to the size of the file when it was created, whichever is greater.
It is not possible to shrink a read-only database.
The status of this option can be determined by examining theIsAutoShrinkproperty of the DATABASEPROPERTYEX function.When set to ON, the database files are candidates for periodic shrinking. Both data file and log files can be shrunk automatically by SQL Server. AUTO_SHRINK reduces the size of the transaction log only if the database is set to SIMPLE recovery model or if the log is backed up.
When set to OFF, database files are not automatically shrunk during periodic checks for unused space. Default is OFF.