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 »
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 »
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 »
Change Data Capture feature of SQL 2008 is based on Transactional Replication. CDC and Transactional Replication used the same internal stored procedure sp_replcmds to retrieve data updates from the transaction log. However, unlike Transactional Replication, CDC does NOT require the tables to have a unique index (or Primary Key). In fact CDC can be use
Read More »
Vijay Rodrigues | Microsoft SQL Server Support SQL Server Management Studio provides a way to monitor events, such as replication agent events, using alerts. SQL Server includes a set of predefined alerts for replication agents. If you would like to start the monitoring for replication agent failures, please follow below steps. The below is configured
Read More »