Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Truncating the transaction log
Besides scheduling online backups, it is also possible to create a maintenance plan for the transaction logs so they are truncated regularly. If log entries are never deleted from the transaction logs, the logical logs grow until they consume all available space on the disks holding the physical log files. At some point, old log records that are no longer necessary for recovering or restoring a database must be deleted to make way for new log records. The process of deleting these log records, to reduce the size of the logical log, is seen as truncating the log.
A maintenance plan should be created using the AppSync Transaction Log backup feature. It should occur at regular intervals that keep the transaction log from growing past the wanted size. It means that the sequence of log backups must contain every log record that was written since the database backup. When a sequence of transaction log backups is maintained, no log record can be truncated until after it has been written to a log backup. Do not confuse with active logs(.ldf) and transaction log backups. The latter is a production of backing up the former. Only the transaction log backup can be used in the roll-forward procedure.