Share this PostWorking with a customer to setup a large subscriber we noticed the Merge Agent was NOT doing a BULK INSERT, but instead was doing row-by-row insert. This had significant overhead for the Merge Agent resulting in longer then expected initial/reinit synchronization times. Downloaded 33 change(s) in 'Customer' (33 inserts): 33 total Applied the
Read More »
Share this PostNew for SQL 2008 is the ability for the Distribution Agent to push updates to the Subscriber using multiple connections. This feature, called Subscription Streams, only works when replicating transactions as stored procedures and not TSQL statements. See: Enhancing Transactional Replication Performance (Use the –SubscriptionStreams parameter for the Distribution Agent.) Background The published
Read More »
Share this PostError messages: Unable to decide if MakeGeneration is needed. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199360) Get help: http://help/MSSQL_REPL-2147199360 Query timeout expired (Source: MSSQLServer, Error number: 0) Get help: http://help/0 The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When
Read More »
Share this PostContent 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
Read More »
Share this PostJosé 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
Read More »