Database Reference
In-Depth Information
Figure 29-13. FULL and BULK-LOGGED recovery models: Initial Stage
After another transaction log backup, SQL Server can truncate VLF3. However, VLF4 must remain active because
the Replication Log Reader has yet to process some of the log records from VLF4. Figure 29-14 illustrates this point.
Figure 29-14. FULL and BULK-LOGGED recovery models: Log truncation
As you can see, in the FULL or BULK-LOGGED recovery models, the active part of transaction log starts with VLF,
which contains the oldest of the following:
LSN of the last log backup
LSN of the oldest active transaction
LSN of the process that reads transaction log records
FULL database backup does not truncate the transaction log. You should perform transaction log backup
in order to do so.
Important
 
 
Search WWH ::




Custom Search