|
Measures reported by MsSqlRepDistDelTest
The Distribution Agent is used with snapshot replication and transactional replication. It applies the initial snapshot to the Subscriber and moves transactions held in the distribution database to Subscribers. The Distribution Agent runs at either the Distributor for push subscriptions or at the Subscriber for pull subscriptions.
If replication is taking longer than usual, you may want to check how each of the agents involved in the replication process is performing, so that you can isolate the agent that could be causing the delay. The Distribution Replication Agent test helps you run frequent health checks on the Distribution agent and reveals whether latencies (if any) in the operations of this agent are the root-cause for the replication slowdown.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| DeliveredCmds |
Indicates the rate at which the Distribution agent delivered commands to the Subscriber. |
Commands/Sec |
|
| DeliveredTrans |
Indicates the rate at which the Distribution agent delivered transactions to the Subscriber. |
Trans/Sec |
A high value is desired for this measure. If the value of this measure dips consistently over time, it is indicative of a slowdown. |
| DeliveryLatency |
Indicates the current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they are applied at the Subscriber. |
MilliSec |
Ideally, the value of this measure should be 0 or very low. A high value indicates that the Distribution agent is taking too much time to push transactions to the Subscriber.
The possible causes for this are as follows:
- A series of transactions could be trying to move a large batch of commands to the Subscribers
- Blocking of the Distribution Agent by another Replication Agent
- Long execution times in the INS/UPD/DEL stored rocedures used to apply transactions to the subscriber
- SQL statements not being replicated as ‘parameters’
|
|