Tag: distribution cleanup

Follow the Data in Transactional Replication Chris SkorlinskiMicrosoft SQL Server Escalation Services Abstract Many technology solutions use a STORE and FORWARD model to move data though out the business. It begins when source data change is detected, collected, and STORED in a cache. This cache data, often on a schedule, is processed and FORWARD to…

Distribution Agent fails with “Could not remove directory” error Sateesh Yele Microsoft SQL Server Support Symptom: The Distribution Clean up job fails with the following error. Executed as user: Domainname\Username. Could not remove directory ‘C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\ReplData\unc’. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. [SQLSTATE…

What Immediate_sync means in Transactional Replication José Moreira NetoMicrosoft 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…

What is a “virtual” Subscription in Transactional Replication 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…