Share this PostAre 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
Read More »
Share this PostI 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
Read More »
Share this PostAmit 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.
Read More »
Share this PostSateesh 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
Read More »
Share this PostAs we know, Transactional Replication moves data from the Publisher to the Distributor then to the Subscribers. When working, data flows near real-time through both of these steps. When problems occur which interrupt this flow, latency is introduced. The challenge is to find which step is contributing to the overall latency. Tracer Tokens
Read More »