Tag: immediate_sync

How to: Initialize a Transactional Subscription from a Backup with Multiple Backup Files

Below is a slight modification to the How to: Initialize a Transactional Subscription from a Backup steps to handle Publisher database backups to multiple BAK FILES. 1)       Execute sp_addpublication (Transact-SQL) at the Publisher on the publication database. Specify a value of true for @allow_initialize_from_backup = N’true’ and @immediate_sync = N’true’ 2)       Create a backup of
Read More »

Snapshot Files deleted when “@immediate_sync = N’true'” and “@retention = 0”.

As mentioned in previous post the @immediate_sync = N’true’ allows you to add a new Transactional Replication subscriber anytime during the Retention Period as both the Snapshot files on disk and the “cached” transactions stored in the distribution database will be available to bring a subscriber up-to-date with the Publisher. One small catch: SQL Distribution
Read More »

What happens if I select Create a snapshot immediately in the Publication Wizard?

When creating a Transactional Replication publication, what happens if I check Create a snapshot immediately and keep the snapshot available to initialize subscriptions? This sets the publication property @property=‘immediate_sync’,@value=‘TRUE’ which instructs Replication to keep all the transactions cached in the Distribution database for the entire Retention Period.  Normally these rows are purged as soon as
Read More »

What Immediate_sync means in Transactional Replication

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 »