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 »
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 »
When Replication the EXECUTION of a stored procedure to a subscriber select the “serialized transaction” and and wrap the SP execution within a transactions. This ensures the changes are replicated as a single stored procedure execution and not as individual row-level updates. See: Publishing Stored Procedure Execution in Transactional Replication “The serializable option is recommended
Read More »
Here is a great posting by Kevin Locke on a problem he encountered when data modifications occurred near the top of a complicated replication filter configuration. These changes can cause “partition change” which triggers re-evaluation of all child data; also known as “repartitioning”. Kevin’s solution was to add an index to the Merge tracking tables,
Read More »