Stop replication methods

Classic data servers handle a request to stop replication differently, depending on what method is chosen.

Controlled

Allows all transactions that are in progress to finish before replication stops for the subscription. When this method is used, any transaction that is being sent to the target server is completely sent, and any transactions that are in the subscription's apply cache at the target server are applied before replication stops for the subscription. Following a controlled stop, the subscription is placed in an inactive state. The capture service continues to read log data for the subscription in anticipation of a subsequent START command for the subscription. The subscription's apply cache is retained, but it is empty. This is the default.

Immediate

Stops all transactions immediately and rolls back any transactions that are not finished. Following an immediate stop, the subscription is placed in the inactive state. The capture service continues to read log data for the subscription. The apply cache and its contents are retained in anticipation of a subsequent START command for the subscription.

Scheduled End

If the source server receives a request for a scheduled end of replication, transactions stops when the source server receives a unit of recovery (UOR) that occurred after the specified scheduled end date. This UOR is not replicated and initiates the end of replication.