Initialization of Merge Replication subscriber fails with primary key violation

Initialization of Merge Replication subscriber fails with primary key violation Troy Moen Microsoft SQL Server Escalation Services We encountered an unusual timing problem while pushing a Snapshot down to a merge subscriber.  We don’t expect many to encounter this problem, after all we’ve only seen it once in 15 years.  We wanted to share this…

0

Follow the Data in Transactional Replication

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…


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

How to: Initialize a Transactional Subscription from a Backup with Multiple Backup Files Chris Skorlinski Microsoft SQL Server Escalation Services 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…

2

All about “Not for Replication”

All about “Not for Replication” Rishi Maini Microsoft SQL Server Escalation Services All about “Not for Replication” “Not for Replication” is a property which can be set for different objects like Check constraints, Foreign Key constraints, Triggers , Identity columns etc while using SQL Server Replication. Feature used when the DBA would like the transactions…