Author: Chris Skorlinski [MSFT]

“Replication Monitor could not insert the tracer token”

I’m seeing an uptick in customers using combination of AlwaysOn and Transactional Replication. Some are configuring the Publisher for high-availability, and some are configuring the Subscriber with Read-Only Secondary to prevent contention from the Distribution Agent updates and “reporting” read queries. Once configured, Tracer Tokens are often used to monitor end-to-end Transactional Replication Latency. Tracer
Read More »

KB article 312292 How to enable replication agents for logging to output files in SQL Server

While troubleshooting SQL Server Replication we often want to capture detail step-by-step execution of Replication Agent.  One technique is to configure the Agent to log its execution to a Text file.  This posting walks through a couple of different ways to accomplish this.  It is also covered in the KB article http://support.microsoft.com/?id=312292.  I’ll use both
Read More »

Enabling Transactional Subscriber with Identity Ranges for Updates

Transactional Replication published tables containing Identity Ranges are updated on subscriber via Replication Distribution Agent.  This processes does not increment the subscriber’s table Identity Seed starting value. If you drop a Subscriber and want to bring it online as an updatable user database, first execute CHECKINDENT reseeding the table to highest value + 1. DBCC
Read More »

Peer 2 Peer Replication fails with Incorrect syntax near ‘sp_MS…’ (Source: MSSQLServer, Error number: 102)

Symptom Creating a Peer 2 Peer publication from SQL scripts and you observe the Distribution Agents failing with “incorrect syntax near”. These messages can be observed in SQL Server Agent job history, in SQL Profiler Trace, or in Agent -Output logging. Errors show below were raised on (insert) stored procedure for Production.Product table for AdventureWorks2017
Read More »