New Peer Initialization (Peer-to-Peer Replication)

THIS TOPIC APPLIES TO: yesSQL ServernoAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Use the New Peer Initialization page to specify how peer databases were initialized. (Peers must be initialized before you complete this wizard.) Peers are initialized manually or by using the initialize with backup functionality that is provided by transactional replication. (Peer-to-peer transactional replication does not support initializing peers by using a snapshot.) If different peers have to be initialized using different methods, you must add the peers separately by running the wizard multiple times.

Options

Specify how the new peer database(s) was initialized
The schema and data for all published objects must be present at each peer. Select one of the following options:

  • Select the first option if you have manually created the schema for published objects or you have restored a backup, and no data changes have been made at the first publication database since the backup was taken. If you created the schema manually, you must ensure that all required data is present at each peer. This option corresponds to a value of replication support only for the subscription property sync_type.

  • Select the second option if you have restored a backup, and data changes have been made at the first publication database since the backup was taken. Replication must now deliver changes from the first publication database that were not included in the backup. This option corresponds to a value of initialize with backup for the subscription property sync_type.

    When a publication is enabled for peer-to-peer replication, the allow_initialize_from_backup publication property is set. Replication immediately starts to track changes in the first publication database. Therefore, these changes can be delivered to a restored database at one or more peers if the initialize with backup option is selected. Click the Browse button to locate the backup used, and replication will read the log sequence number (LSN) from the backup. All changes in the first publication database that have a higher LSN will be delivered to each peer.

    This option might not be available if you are creating or adding to a topology that includes SQL Server 2005. The following table shows whether the option is available when you are adding a node to an existing topology.

    New node First node Additional nodes Option
    SQL Server 2005 SQL Server 2005 SQL Server 2005 Disabled
    SQL Server 2005 SQL Server 2008 None Disabled
    SQL Server 2008 SQL Server 2008 SQL Server 2005 Disabled
    SQL Server 2005 SQL Server 2005 None Enabled
    SQL Server 2008 SQL Server 2008 None Enabled
    SQL Server 2008 SQL Server 2008 SQL Server 2008 Enabled
    SQL Server 2008 SQL Server 2005 None Enabled

See Also

Administer a Peer-to-Peer Topology (Replication Transact-SQL Programming)
Peer-to-Peer Transactional Replication