The database logs for transactional publishing will become larger and larger.

The regular backup log will automatically cut off the backup and it will not become larger and larger. However, you need to pay attention to some options for Publishing Database Log backup and transactional Publishing.

The distribution database can be restored to the last backup state without re-configuring replication or re-initializing subscription. Generally, the Log Reader Agent connects to the Publishing Database, scans logs and retrieves the collection of the next n transactions to be copied, and propagates these transactions to the distribution database, then inform the publishing database that the transaction has been successfully committed in the distribution database.

In this case, the published database can truncate the log portion that contains these transactions (as long as the transaction has been backed up ). If the distribution database fails at this time and is restored to the previous backup status, the Log Reader Agent may not be able to send the missing transactions because the log portion containing these transactions may have been truncated.

Setting the sync with backup option on the distribution database ensures that all transactions are not truncated before they are propagated to the distribution database. You can also ensure that the distributed database that contains new transactions is backed up. The distribution database can be restored to the last backup status, and the Log Reader Agent can transmit the transactions missing from the restored distribution database. Replication will continue without any impact.

To back up the distribution database more frequently by backing up the transaction log and setting the sync with backup option, you must set the trunc. Log On chkpt option of sp_dboption on the distribution database to false.

Unlike the Publishing Database, setting the sync with backup option on the distribution database does not affect the replication lag time, but it will delay the log Truncation on the publishing database, the transaction in the distribution database is backed up. The sync with backup option is available only when the publisher and distributor run SQL Server 2000.