Author: Chris Skorlinski [MSFT]

Msg 21892, Level 16, State 1

ecently I posted Repltalk a walkthrough setting up Publisher, Distributor, and Subscriber each in AlwaysOn Availability groups. In this series of postings, I’m going to break then, show you what went wrong, and how to fix it. Let’s start with error message when attempting to validate a redirected publisher. [crayon-5df64add090e5916682321/] Msg 21892, Level 16, State
Read More »

Walkthrough Publisher, Distributor, Subscriber in AlwaysOn Availability Groups

The steps below walkthrough setting SQL Server 2016 Replication Publisher, Distributor, and Subscriber each in an Always On Availability Group with one set of replicas residing one 1 subnet and 2nd set on another subnet simulating 2 different data centers (Pub1, Dist1, Sub2) <–> (Pub2, Dist2, Sub2). These steps below combine the following postings: Configure
Read More »

“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 »