Makes a copy of the selected subscription and prompts you to supply a subscription name for the copy. Although you can change Destination options for a duplicate subscription, the Duplicate command permanently assigns the duplicate subscription to the same logical source as the original. To use a different source, create a new subscription rather than duplicating an existing one.
|
WARNING |
Except for the subscription name, duplicate snapshot subscriptions are created with the same settings as the original subscription, including the Destination and Replication options and the Schedule settings. Since some of the Destination Option settings can affect the destination table when a subscription is saved or run, and the duplicate subscription inherits the same destination options as the original subscription, you must be careful to avoid inadvertent loss of data when creating a duplicate subscription. If the original subscription uses the destination options discussed below, you may need to change the Destination Options in the original subscription before you create a duplicate subscription from it. |
If the original snapshot subscription is set to create or re-create the table when the subscription is saved or a snapshot replication is run, and if the original destination table exists when you click OK in the Duplicate Subscription dialog, the Data Replicator Manager asks if you want save the subscription even though it will drop and re-create the existing destination table. If you click Yes, the destination table is dropped and re-created, but the timing for this action varies depending on the original subscription settings, as follows:
For a subscription that is set to create the table when the subscription is saved, the destination table is dropped and re-created as part of the process of creating the duplicate subscription. Data previously residing in the table is lost before you can modify either subscription.
For a subscription that is set to re-create the table when Re-Create Table On Each Replication, the destination table is dropped and re-created the next time you run the subscription. Depending on the replication schedule for the subscription, the wait until replication time can give you an opportunity to edit subscription properties so that one of the two snapshot subscriptions will use a different destination table.
If the original subscription is set to Use Existing Table, the original destination table is not affected until replication time, when its rows may be truncated, deleted, or appended to, as specified by the running subscription's other Destination Options setting. Depending on the replication schedule for the two subscriptions, the wait until replication time can give you an opportunity to edit subscription properties so that one of the two subscriptions will use a different destination table.