I'm analyzing the distribution database to see if there any latency in the replication between publisher and subscriber
The architecture is one publisher, 1 distrubution db (on publisher server) and one subscriber on different server.
I would also like to build a custom historical log table that can contain a record of any latency issues over the past month. Looking at the distribution db there is a table called MSdistribution_history . But the latest row in this table is constantly changing e.g the comment could say "61 transactions with 230 commands delivered" . If I query the table in 5 seconds later the latest row will say have updated again and I'm having trouble understanding what this data means. Anyway I can't keep polling this table every few seconds, can you explain what is the best way to track latency over time and better understand the data in this table ?