Share this PostOne key parameter to consider when performing batch updates against tables enabled for Merge Replication is ‘generation_leveling_threshold’. This setting controls how many data changes should be grouped into one generations (or batch). The Merge Agent then collect and sends those batches of changes based on the Merge Agent [-DownloadGenerationsPerBatch] parameter. The default is
Read More »
Share this PostHere is another customer question about Replication I thought worth sharing. I am using SQL Server 2008 64 bits. I have to change the location of the data file (i.e. MDF file). I was planning to detach and attach. DB is also using Transactional Replication so I can’t detach the DB. Is there
Read More »
Share this PostLatency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers. The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of these queries to look for
Read More »
Share this PostContent Provided by: Paul King, Microsoft One of the most important things to watch out for with change data capture is the transaction log I/O subsystem. As stated earlier, log file I/O significantly grows when change data capture is enabled in a database. In addition to that, log records stay active until change
Read More »
Share this PostThe “default” Agent Profile enables “-HistoryVerboseLevel 1” which provides limited detail in the Distribution database history tracking tables. Using Replication Agent Profile “Verbose history agent profile.” enables “-HistoryVerboseLevel 2” which provides additional diagnostic data while troubleshooting SQL Server Replication. The “Verbose history agent profile.” can be set using Replication Monitor for all types
Read More »