A customer recently noticed their Published database transaction log would continue to grow until they backed up the Distribution database. [crayon-64844c8125c90054535878/] “… to clear out the Transaction Log file was to backup the Distribution Database System – this appeared to work and the stuck transaction was shifted onwards, as the transaction log file had grown
Read More »
José Moreira Neto | Microsoft SQL Server Escalation Services sp_addpublication parameter: [ @immediate_sync=] ‘immediate_synchronization’ Immediate_sync has a default of FALSE. independent_agent must be true for immediate_synchronization to be true. Immediate_sync feature instructs Replication to maintain Snapshot BCP files and distributed transactions in the Distribution database should a new subscriber be created (or reinit) within the
Read More »
The SQL Replication system table syssubscriptions contains one row per published article per subscriber. Notice the “virtual” subscriber. With the immediate_sync property is set to true, “virtual” subscriptions are created as placeholders for retaining generated snapshot (transactions). These “virtual” subscriptions are activated just like normal subscriptions by the Snapshot agent and are used to track
Read More »