“Replication Monitor could not insert the tracer token”

Chris SkorlinskiMicrosoft SQL Server Escalation Services We’re 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…


Transaction Log won’t truncate when using Snapshot Replication to Azure SQLDB

Chris SkorlinskiMicrosoft SQL Server Escalation Services Customer encountered transaction log growth for a Published SQL Server 2016 database while nightly refreshing Azure SQLDB. We discovered the default publication setting “replicate_dll” was still enabled. SELECT [description],[name],[replicate_ddl] FROM <your published database>.[dbo].[syspublications] description name replicate_ddl —————————————————— ———- ————- Snapshot publication of database ‘AdventureWorks2014’ Customers 1 (1 row(s) affected)…