Sateesh Yele | Microsoft SQL Server Support Symptom Distribution Agent is failing when connecting to subscriber server when replicating between cross domain servers. Consider this, you are setting up replication between 64 bit edition servers that are cross domain and the Distribution Agent is failing with the following error in Replication Monitor. The process could
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 »
Any Cox | Microsoft Premier Field Engineer We recently encounter the a problem where Replication Distribution Agent failed with error below while trying to replicate the “execution” of a stored procedure. Msg 0, Level 20, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. Executing
Read More »
Anurag Sharma | Microsoft SQL Server Escalation Services Background In many cases customer often have large databases published and creating a snapshot of such large database is always a pain. And, even when published databases are of manageable size, a slow or unreliable network link can further complicate the issue. From SQL Server 2005 onwards
Read More »
José Moreira Neto | Microsoft SQL Server Escalation Services sp_addpublication parameter: [ @immediate_sync=] ‘immediate_synchronization’ Immediate_sync has a default of FALSE. independent_agent must be true for immediate_synchronization to be true. Immediate_sync feature instructs Replication to maintain Snapshot BCP files and distributed transactions in the Distribution database should a new subscriber be created (or reinit) within the
Read More »