Eric Lucht | Microsoft SQL Server Escalation Services Centralized troubleshooting refers to the ability to generate detailed Merge agent log files on both client and Web server (for Web Synchronization), and gather the log files into a central location on the publisher as part of the sync process, no matter where the reconciler is run.
Read More »
Eric Lucht | Microsoft SQL Server Escalation Services Logging Options When the Merge subsystem is initialized, agent logging is automatically enabled using default values. The Agent will begin logging in the replmerg.log being created in the 100\COM (90\COM for SQL 2005) folder. This blog posting covers registry keys used to override the logging level of
Read More »
Sateesh Yele | Microsoft SQL Server Support I would like to share information about an interesting Replication issue I recently worked. Customer was getting unusual error messages during synchronization. Symptom: Merge agent is failing with the following error message when validating large tables with checksum. The merge process was unable to perform data validation on
Read More »
Why does Microsoft SQL Support ask me all those questions? Why can’t they just show me how it work or fix the problem? Well wish it was that simple, but for us to help you we need to get the “big picture”. Below are some of the questions we ask and initial troubleshooting steps we’ll
Read More »
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 “best practices” below are in no particular order. My objective was to
Read More »