How SQL Server changes the size of a package

Since the replication of the thought can be a safe sleep, who do not know that the problem ensued

The problem is to lose the packet , do not know the situation of the reader can first look at me before the "SQL Server monitoring replication and use the Database Mail function to send alarm mail"

Because the engine room C and room A is not a LAN, the network condition is not too good

Distribution backlog of commands are often in 20w+ , replication does not error, each delivery of less than 30 transactions, normally SQL Server by default will transfer 100 transactions each time

Then I tested the network.

Ping subscribers from the Distributor, ping 4096Byte packages, ping100 times, because the distribution default transmission packet size is 4096Byte, occasionally timeout in the middle

Ping  subscriber IP-  l 4096-N 100

Parameter l refers to the size of the package, parameter n refers to the number of pings, without the-l parameter, the default ping package size is 32Byte