The Transaction Log (SQL Server)
Every SQL Server database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log must be truncated on a regular basis to keep it from filling up. However, some factors can delay log truncation, so monitoring log size is important. Some operations can be minimally logged to reduce their impact on transaction log size.
The transaction log is a critical component of the database and, if there is a system failure, the transaction log might be required to bring your database back to a consistent state. The transaction log should never be deleted or moved unless you fully understand the ramifications of doing this.
Known good points from which to begin applying transaction logs during database recovery are created by checkpoints. For more information, see Database Checkpoints (SQL Server).
In this Topic:
Benefits: Operations Supported by the Transaction Log
The transaction log supports the following operations:
Recovery of individual transactions.
Recovery of all incomplete transactions when SQL Server is started.
Rolling a restored database, file, filegroup, or page forward to the point of failure.
Supporting transactional replication.
Supporting high availability and disaster recovery solutions: Always On Availability Groups, database mirroring, and log shipping.
Transaction Log Truncation
Log truncation frees space in the log file for reuse by the transaction log. Log truncation is essential to keep the log from filling. Log truncation deletes inactive virtual log files from the logical transaction log of a SQL Server database, freeing space in the logical log for reuse by the Physical transaction log. If a transaction log were never truncated, it would eventually fill all the disk space that is allocated to its physical log files.
To avoid this problem, unless log truncation is being delayed for some reason, truncation occurs automatically after the following events:
Under the simple recovery model, after a checkpoint.
Under the full recovery model or bulk-logged recovery model, if a checkpoint has occurred since the previous backup, truncation occurs after a log backup (unless it is a copy-only log backup).
For more information, see Factors That Can Delay Log Truncation, later in this topic.
Log truncation does not reduce the size of the physical log file. To reduce the physical size of a physical log file, you need to shrink the log file. For information about shrinking the size of the physical log file, see Manage the Size of the Transaction Log File.
Factors That Can Delay Log Truncation
When log records remain active for a long time transaction log truncation is delayed, and potentially the transaction log can fill up.
For information about how to respond to a full transaction log, see Troubleshoot a Full Transaction Log (SQL Server Error 9002).
Log truncation can be delayed by a variety of factors. You can discover what, if anything, is preventing log truncation by querying the log_reuse_wait and log_reuse_wait_desc columns of the sys.databases catalog view. The following table describes the values of these columns.
|log_reuse_wait value||log_reuse_wait_desc value||Description|
|0||NOTHING||Currently there are one or more reusable virtual log files.|
|1||CHECKPOINT||No checkpoint has occurred since the last log truncation, or the head of the log has not yet moved beyond a virtual log file. (All recovery models)
This is a routine reason for delaying log truncation. For more information, see Database Checkpoints (SQL Server).
|2||LOG_BACKUP||A log backup is required before the transaction log can be truncated. (Full or bulk-logged recovery models only)
When the next log backup is completed, some log space might become reusable.
|3||ACTIVE_BACKUP_OR_RESTORE||A data backup or a restore is in progress (all recovery models).
If a data backup is preventing log truncation, canceling the backup operation might help the immediate problem.
|4||ACTIVE_TRANSACTION||A transaction is active (all recovery models).
A long-running transaction might exist at the start of the log backup. In this case, freeing the space might require another log backup. Note that a long-running transactions prevent log truncation under all recovery models, including the simple recovery model, under which the transaction log is generally truncated on each automatic checkpoint.
A transaction is deferred. A deferred transaction is effectively an active transaction whose rollback is blocked because of some unavailable resource. For information about the causes of deferred transactions and how to move them out of the deferred state, see Deferred Transactions (SQL Server).
Long-running transactions might also fill up tempdb's transaction log. Tempdb is used implicitly by user transactions for internal objects such as work tables for sorting, work files for hashing, cursor work tables, and row versioning. Even if the user transaction includes only reading data (SELECT queries), internal objects may be created and used under user transactions. Then the tempdb transaction log can be filled.
|5||DATABASE_MIRRORING||Database mirroring is paused, or under high-performance mode, the mirror database is significantly behind the principal database. (Full recovery model only)
For more information, see Database Mirroring (SQL Server).
|6||REPLICATION||During transactional replications, transactions relevant to the publications are still undelivered to the distribution database. (Full recovery model only)
For information about transactional replication, see SQL Server Replication.
|7||DATABASE_SNAPSHOT_CREATION||A database snapshot is being created. (All recovery models)
This is a routine, and typically brief, cause of delayed log truncation.
|8||LOG_SCAN||A log scan is occurring. (All recovery models)
This is a routine, and typically brief, cause of delayed log truncation.
|9||AVAILABILITY_REPLICA||A secondary replica of an availability group is applying transaction log records of this database to a corresponding secondary database. (Full recovery model)
For more information, see Overview of AlwaysOn Availability Groups (SQL Server).
|10||—||For internal use only|
|11||—||For internal use only|
|12||—||For internal use only|
|13||OLDEST_PAGE||If a database is configured to use indirect checkpoints, the oldest page on the database might be older than the checkpoint LSN. In this case, the oldest page can delay log truncation. (All recovery models)
For information about indirect checkpoints, see Database Checkpoints (SQL Server).
|14||OTHER_TRANSIENT||This value is currently not used.|
|16||XTP_CHECKPOINT||When a database has a memory-optimized filegroup, the transaction log may not truncate until automatic In-Memory OLTP checkpoint is triggered (which happens at every 512 MB of log growth).
Note: To truncate transaction log before 512 MB size, fire the Checkpoint command manually against the database in question.
Operations That Can Be Minimally Logged
Minimal logging involves logging only the information that is required to recover the transaction without supporting point-in-time recovery. This topic identifies the operations that are minimally logged under the bulk-logged recovery model (as well as under the simple recovery model, except when a backup is running).
Minimal logging is not supported for memory-optimized tables.
Under the full recovery model, all bulk operations are fully logged. However, you can minimize logging for a set of bulk operations by switching the database to the bulk-logged recovery model temporarily for bulk operations. Minimal logging is more efficient than full logging, and it reduces the possibility of a large-scale bulk operation filling the available transaction log space during a bulk transaction. However, if the database is damaged or lost when minimal logging is in effect, you cannot recover the database to the point of failure.
The following operations, which are fully logged under the full recovery model, are minimally logged under the simple and bulk-logged recovery model:
When transactional replication is enabled, BULK INSERT operations are fully logged even under the Bulk Logged recovery model.
SELECT INTO operations.
When transactional replication is enabled, SELECT INTO operations are fully logged even under the Bulk Logged recovery model.
Partial updates to large value data types, using the .WRITE clause in the UPDATE statement when inserting or appending new data. Note that minimal logging is not used when existing values are updated. For more information about large value data types, see Data Types (Transact-SQL).
The WRITETEXT and UPDATETEXT statements are deprecated, so you should avoid using them in new applications.
If the database is set to the simple or bulk-logged recovery model, some index DDL operations are minimally logged whether the operation is executed offline or online. The minimally logged index operations are as follows:
CREATE INDEX operations (including indexed views).
ALTER INDEX REBUILD or DBCC DBREINDEX operations.
The DBCC DBREINDEX statement is deprecated so you should avoid using it in new applications.
DROP INDEX new heap rebuild (if applicable).
Index page deallocation during a DROP INDEX operation is always fully logged.
Managing the transaction log
Backing Up the Transaction Log (Full Recovery Model)
Restoring the Transaction Log (Full Recovery Model)
Control Transaction Durability
Prerequisites for Minimal Logging in Bulk Import
Back Up and Restore of SQL Server Databases
Database Checkpoints (SQL Server)
View or Change the Properties of a Database
Recovery Models (SQL Server)