If you need to reset your Replication topology you can quickly rebuild subscribers using the “no initialize” also called “Replication Support Only (RSO)”. WARNING: These steps are designed to remove ALL of your Replication configuration and settings, recreating with new metadata tables. The RSO option skips the Snapshot data reinitialization phase. It only pushed down new
Read More »
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 »
Sakthivel Chidambaram | Microsoft SQL Server Support There are situations where you initialize a Transactional subscription from a backup and later you need to add an article. If the publication was created using Snapshot Replication, you can re-run the Snapshot Agent and only the newly added article is BCP’ed out then BCP’ed in at the
Read More »
I thought it would be helpful to post a Replication Distribution Agent troubleshooting case to show more about replication components and troubleshooting approaches. Problem: SQL Server Distribution Agent reported “Failed” in Replication Monitor. To capture text of the message we added the following parameters to the Distribution Agent job and restarted the job. The –output
Read More »
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 »