distribution database
-
Tracking Replication Errors
Continuing our Replication Monitoring series, this fourth installment explores how to surface a couple metrics that highlight ongoing replication errors. Our goal is simple: provide immediate visibility into where failures are occurring so that DBAs can intervene at the correct point in the pipeline to begin their investigation. While we are focusing specifically on Transactional… Continue reading
-
Monitor and Analyze Replication Undistributed Commands
Instead of relying on Replication Monitor to assess subscriber health and identify pending commands, we can query the msrepl_commands table in the distribution database directly. This approach allows us to analyze undistributed commands by various attributes, providing a deeper understanding of the throughput across the entire replication environment. Furthermore, we can port these metrics into… Continue reading
-
Monitoring the distribution database size
Part 2 of the Replication Monitoring Series We can answer the question, ‘Is the replication environment healthy?’ with a single monitoring metric: the size of the distribution database. Because the distribution database functions largely as a queue, it should remain relatively small. The Distributor holds replication commands from the Publisher only until all Subscribers have… Continue reading