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 »
Abstract Many technology solutions use a STORE and FORWARD model to move data though out the business. It begins when source data change is detected, collected, and STORED in a cache. This cache data, often on a schedule, is processed and FORWARD to one or more destinations. Microsoft technologies using “store and forward” include Log
Read More »
José Moreira Neto Microsoft SQL Server Escalation Engineer Certain table reindex operations, like online reindex or reindex operation while database is running in full recovery model, will create large amounts of transaction log records in the database transaction logs. This may or may not generate an actual increase in the physical size or the transaction
Read More »
As we know, Transactional Replication moves data from the Publisher to the Distributor then to the Subscribers. When working, data flows near real-time through both of these steps. When problems occur which interrupt this flow, latency is introduced. The challenge is to find which step is contributing to the overall latency. Tracer Tokens help you
Read More »
Tracer Tokens are a great way to monitor the flow of transactions from the Publisher to the Subscriber. These can be generated and tracked from SQL Server Replication Monitor or via TSQL commands. This post includes some of the common TSQL commands used to generate and track Tracer Tokens. Details can be found on SQL
Read More »