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 Agents default to use the “Verbose History Agent Profile”. In SSMS, right click the Replication
Read More »
I hope to answer the question “What is the difference between Push and Pull Merge Replication?” in this blog posting. As you know Merge Replication is all about merging or blending changes between multiple SQL Servers. One SQL Server is designated as the PUBLISHER or “master” copy of the database. Changes made on the Publisher
Read More »
reposting from Claudia Silva Microsoft SQL Escalation Services United Kingdom http://blogs.technet.com/b/claudia_silva/ Problem: The upload message to be sent to Publisher ‘XXX’ is being generated The merge process is using Exchange ID ‘XXXXX’ for this web synchronization session. No data needed to be merged. Request message generated, now making it ready for upload. Upload request size
Read More »
Working with a customer to setup a large subscriber we noticed the Merge Agent was NOT doing a BULK INSERT, but instead was doing row-by-row insert. This had significant overhead for the Merge Agent resulting in longer then expected initial/reinit synchronization times. Downloaded 33 change(s) in 'Customer' (33 inserts): 33 total Applied the snapshot and
Read More »
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 conflict resolver (which is specified when an article is added to a
Read More »