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 »
José Moreira Neto | Microsoft SQL Server Escalation Services Particularities of Merge Anonymous Subscribers In Merge Replication, anonymous subscriptions are required if you want to create a subscription without registering the subscription at the Publisher. This is necessary for cases in which you cannot establish a SQL Server connection to the Publisher during subscription configuration.
Read More »
Eric Lucht | Microsoft SQL Server Escalation Services Logging Options When the Merge subsystem is initialized, agent logging is automatically enabled using default values. The Agent will begin logging in the replmerg.log being created in the 100\COM (90\COM for SQL 2005) folder. This blog posting covers registry keys used to override the logging level of
Read More »