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 »
Are the queries to pull data from the Merge Subscribe taking longer then when executed on the Publisher? Looks like it is time to review the index structure for these tables. We encountered an unusual problem in SQL 2005/2008 where the indexes didn’t get created on the Subscriber when the Snapshot was pushed by the
Read More »
I recently got a customer call where the SQL 2008 Snapshot Agent appeared to hang when started from SSMS. As you can see, pop-up status window shows “Starting agent”. So, looks like its running, but it stays this way forever. Replication Monitor also shows as “Running”. If I double-click the I can zoom in on
Read More »
Amit Banerjee | Microsoft SQL Server Support TSQL Code: MS_MergeAgentStatistics.sql script located on SkyDrive MergePerformance or TechNet Code Share I have sometimes found the need to track the performance of the Merge Agents configured on the server without having to dig through the Replication Monitor or through the Merge Agent job history outputs. So, here
Read More »