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 »
Sometimes MS SQL Replication developers use similar names for similar meaning but which can have very different results. These settings both specify alternate location for the Snapshot files, however, one is set at the publication and one at an individual subscriber. alt_snapshot_folder The alt_snapshot_folder parameter is set at the Publisher for ALL subscribers. This can
Read More »
José Moreira Neto | Microsoft SQL Server Escalation Services Problem 1: batch updates 1) A single update command can generate a transaction with thousands of commands. For example if you execute an UPDATE statement that updates 10K rows on the publisher, up to 20K commands can be send over to the subscriber. On the publisher
Read More »
As 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 help you
Read More »