One 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 to group
Read More »
Content provided by: Steve Dybing, Microsoft SQL Server Support Background on Merge Conflicts ———————————————- When a Publisher and a Subscriber are connected and synchronization occurs, the Merge Agent detects if there are any conflicts. If conflicts are detected, the Merge Agent uses a conflict resolver (which is specified when an article is added to a
Read More »
José Moreira Neto Microsoft SQL Server Escalation Engineer Certain table reindex operations, like online reindex or reindex operation while database is running in full recovery model, will create large amounts of transaction log records in the database transaction logs. This may or may not generate an actual increase in the physical size or the transaction
Read More »
Content provided with help of Jonathan Clark, Microsoft SQL Server Escalation Services Oracle to SQL Server replication is used to support customers migrating Oracle legacy application to Microsoft SQL Server. The data changes in Oracle can be replicated near real-time to a SQL Server database. Here is a little background information on the Oracle to
Read More »
Sakthivel Chidambaram | Microsoft SQL Server Support There are situations where you initialize a Transactional subscription from a backup and later you need to add an article. If the publication was created using Snapshot Replication, you can re-run the Snapshot Agent and only the newly added article is BCP’ed out then BCP’ed in at the
Read More »