Share this PostI’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
Read More »
Share this PostWhile 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
Read More »
Share this PostHere is an interesting support call where Change Data Capture (CDC) log scan job was failing with error below. Error Executed as user: domain\svc_account. Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated problems. [SQLSTATE 42000] (Error 22859)
Read More »
Share this PostSateesh Yele | Microsoft SQL Server Support How to initialize the subscriber from backup Create the publication using user interface Replication Wizard. Under subscription options for the publication, set “allow initialization from backup files” to true Create a new full backup of the publisher database. If you have existing full backup of the
Read More »
You can customize the Transaction and Commands delete batch size to delete in larger increments during distribution database cleanup.