Publication status and history

You’ll notice that the first item in the list in the Snapshot that succeeded. This was the initial synchronization that occurred when we created the subscription. The next item is the LogReader process. This process scans the transaction log of the pubs database to determine if a new transaction has been processed that needs to be replicated. When it detects a transaction that needs to be replicated, the transaction is moved to the distribution database. The final item in this list is the distribution agent. This is the pubs_repl entry that is a push subscription. This agent picks up any new transactions the Log Reader has moved to the distribution database and sends them to the subscriber. On an active replication system, the Log Reader and distribution agents will normally be listed as active as they move transactions around. In this view, they are idle, because there are no current transactions to process.

Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40