The Distribution database is a cache of undistributed commands that the Distribution SQL Agent jobs are responsible to deliver to their subscribers. This cache is populated by the Publisher LogReader Agent job as new data changes are detected. The primary tables holding the cache of undistributed data is MSrepl_transactions and MSrepl_commands.
Latency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers. The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of these queries to look for unexpected high-volume
Read More »
In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber. In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »