Merge metadata cleanup changes in SQL Server 2012 SP2 and SQL Server 2014 SP1

  Content provided by: Hugo Nunes, Microsoft Support Escalation Engineer TITLE: Merge metadata cleanup changes in SQL Server 2012 SP2 and SQL Server 2014 SP1 Abstract: This article briefly describes the change in the merge metadata cleanup logic introduced in SQL Server 2012 SP2 and SQL Server 2014 SP1, and provides some recommendations Terms and…


Primary Key design considerations for Merge Replication

by Holger Linke, Microsoft SQL Escalation Engineer GUIDs and Clustered Indexes Uniqueness is a key factor when synchronizing data between SQL Server/Azure and multiple endpoints like Slates and Smartphones.  With data simultaneously created and updated on servers and clients, ensuring rows are unique to avoid key collisions is critical.  As you know, each row is…


ReplTip – Troubleshooting sp_msmakegeneration

by Holger Linke, Microsoft SQL Escalation Engineer Symptoms: The merge agent may get stuck without apparent progress, or even fail with a timeout error. If several merge agents are trying to synchronize at the same time, they would block each other, until the agent which is running sp_msmakegeneration finishes the call. If the execution of…


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

How to set HistoryVerboseLevel Profile for all Agent

How to set HistoryVerboseLevel Profile for all Agent Chris Skorlinski Microsoft SQL Server Escalation Services This is a follow up post to my article Using “Verbose history agent profile.” while troubleshooting Replication. Using SQL Server Management Studio you can set a default profile for all Replication Agents.  In this walk through I’ll change ALL Merge…

0

Clearing Resolved Merge Replication Conflicts

Clearing Resolved Merge Replication Conflicts Chris Skorlinski Microsoft SQL Server Escalation Services Content provided by: Steve Dybing, Microsoft SQL Server Support Background on Merge Conflicts ———————————————- When a Publisher and a Subscriber are connected and synchronization occurs, the Merge Agent detects if there are any conflicts. If conflicts are detected, the Merge Agent uses a…

3

Replicating data loaded with BCP or Bulk Insert

Replicating data loaded with BCP or Bulk Insert Chris Skorlinski Microsoft SQL Server Escalation Services Yes you can use both Transactional and Merge Replication to move data inserted using the BCP.exe utility of the Bulk Insert command to Subscribers. Considerations For Transactional Replication By default, Transactional Replication will replicate data loaded via BCP or Bulk…

0

Collection of Merge Replication Best Practices

Collection of Merge Replication Best Practices Chris SkorlinskiMicrosoft SQL Server Escalation Services I’m posting a collection of SQL Server 2008 Merge Replication Best Practices.  The material below includes text from SQL Books Online, other white papers, KB articles, web postings, and little from experience I gained working with SQL Replication for almost 15 years.  The…


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…


ReplTalk Start Here

START HERE for table of contents into ReplTalk BLOG postings This page was created to help organize the key ReplTalk MSDN blog postings by the Microsoft SQL Server Replication Support Team.  We hope these postings provide some insight into how Replication works while we peel back some of the layers in these postings.  Since we…