SQL Replication
-
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
-
Replication Monitoring Series
Over the next few months, I will be writing a series of blog posts to share my experience monitoring a large-scale SQL replication environment. I previously worked for a company where we replicated nearly 40,000 objects from 50 publishers to over 100 subscribers. Due to the scale of our SQL replication topology, the Replication Monitor… Continue reading
-
Tracking the Replication Log Reader Latency

Part 1 of the Replication Monitoring Series There is an existing MSSQLTips.com blog post that shares how to identify the Replication Log Reader latency via Replication Monitor and by querying the Distributor’s distribution system tables. In this blog post, I will share another approach to identify the latency metric by utilizing the Publisher’s log file.… Continue reading