September 25, 2013 at 12:57 pm
Hello, Can anyone please help us understand the MSdistribution_History table better. Here is our problem and what we understood so far:
Randomly in the night, we are getting alerted on replication latency issues. By the time, we open up our computers and remote in, latency issues are gone.
We are trying to understand MSdistribution_History for that particular Publication and we are observing weird thing in it. I will explain what we are observing it first.
our latency window: 3:34AM - 3:39AM
we see a bump in delivered_transactions and its associated delivered_commands and obviously there is and will be current delivery latency for that many number of transactions.
However, if you can see in the attached xl, there is a bump in number of transactions @3:19AM(which was not the cultprit for the alert. Our latency threshold is 5 min) and the alerts started coming in @3:34AM.
From 3:34AM until 3:50AM, we got alerted for latency. In the attached table, we have high latency rate but, no transactions/commands associated with it.
So my question here is, when the synch happened fine until 3:24AM(given the bump in no.of transactions/commands) why are we getting alerts @3:34AM until 3:50AM?
hope I explained it clearly.
Note:*Rev columns are the derived columns - converted the cumulative readings into per session readings
Please shed some light at your earliest convenience.
Thanks
Jagan K
Thanks
Jagan K
September 26, 2013 at 2:47 pm
please.. can someone help me out here:crying:
Thanks
Jagan K
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply