In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber. In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »
High Level Transactional Replication Process Flow I’ve posted this flow before on my BLOG but I wanted to include the stored procedure calls used by Transactional Replication. While troubleshooting Replication performance/latency we’ll try and identify which stored procedure executing from which Replication Agent has the highest IO or highest CPU usage. These usually are a
Read More »
Sateesh Yele | Microsoft SQL Server Support Below is a list of self-help resources or this scenario. These resources are used by Microsoft SQL Replication Support Engineers during an Advisory Services engagement or while troubleshooting Web Synchronization problems. We hope you too find these helpful. Web Synchronization for Merge Replication http://msdn.microsoft.com/en-us/library/ms151763.aspx Topologies for
Read More »
While helping a customer on a Replication issue, we encountered an very unusual error message. An error occurred during decryption. There is no remote user 'distributor_admin' mapped to local user '(null)' from the remote server 'repl_distributor'. Changed database context to 'master'. (Microsoft SQL Server, Error: 15466) There are some key words in this error (‘distributor_admin’,
Read More »
Error 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 troubleshooting, restart
Read More »