You can use a wizard to promote changes in a selected subscription
to an existing subscription in a new environment.
About this task
n this scenario, you have made changes to a subscription
that has already been promoted to another environment. For example,
the subscription may already exist in a project that you have reserved
for testing subscriptions, but you may have made some minor changes
on the subscription. To make sure the subscription in the test environment
includes the changes that you made, you need to promote your changes
to the testing environment.Note: When promoting subscriptions that
replicate temporal tables, only those subscriptions belonging to datastores
that support temporal tables will be available for selection.
When
you are promoting changes to an existing subscription, CDC Replication maintains
synchronization between your source and target tables and you do not
need to set the log position in the new environment. However, if you
are making changes that causes you to lose synchronization between
your source and target tables (such as updating the definition of
a source table), then CDC Replication does
not maintain the log position and you will have to resynchronize your
source and target tables in the original and in the new environment.
For more information on how to synchronize source and target tables
in a table mapping, see Flagging source tables for refresh.
- Click
.
- Right-click on a subscription and select Promote
Subscription.
- Select Promote changes to an existing
subscription.
- Select the subscription to which you want to
promote changes from the Promote To list.
- In the Table Mappings area you can
select one of the following two options and click Next:
- Replace all table mappings in the existing subscription
- Indicates the table mappings in the subscription you are promoting
will replace all existing table mappings in the existing subscription
you are promoting to.
For example, you plan on promoting table mappings
from subscription Develop to subscription Test.
Subscription Develop contains four table mappings: A, B, C,
and D. A and B are
selected for promotion to subscription Test. Subscription Test contains
three table mappings: A, B, and Z.
By selecting this option, table mappings A and B in
subscription Develop will replace all of the
existing table mappings in subscription Test. After
promotion is complete, subscription Test will only
contain table mappings A and B.
Table mapping Z will no longer exist in subscription Test.
- Only replace table mappings from the promoted subscription
- Indicates the table mappings in the subscription you are promoting
will only replace table mappings with identical names in the existing
subscription you are promoting to. All other table mappings will remain
in the subscription you are promoting to.
For example, you plan on promoting table mappings
from subscription Develop to subscription Test.
Subscription Develop contains four table mappings: A, B, C,
and D. A and B are
selected for promotion to subscription Test. Subscription Test contains
three table mappings: A, B, and Z.
By selecting this option, table mappings A and B in
subscription Develop will only replace table mappings A and B in
subscription Test. After promotion is complete, subscription Test will
still contain three table mappings: A, B and Z.
- Confirm the source datastore and the name of
the database and owner from which you want to promote the changes,
then click Next.
When promoting
subscriptions that replicate temporal tables, only datastores that
support temporal tables will be available for selection.
If you have built a derived column on the source
that references another table in another database using the %GETCOL column
function, specify the name of the database and owner that contains
the table that is referenced in the %GETCOL function. Also, make sure
that the table referenced in the derived column exists in the new
source database.
- Confirm the target datastore and the name of
the database and owner to which you want to promote the changes.
- If you have configured expressions with column
functions that call user exit programs, such as
%USER or %STPROC,
specify the full path that contains the stored procedure, or the name
of the user exit program referenced in the expression, then click
Next. Make sure that the stored
procedure or user exit program already exists in the new source database.
- If you have built a derived column, an expression,
or a row-filtering expression that uses the
%SELECT column
function, confirm the list of displayed expressions and click Next.
After promotion, make sure that the table or column referenced
in the %SELECT expression exists in the new database.
- Click View XML to confirm
the location and attributes of the promoted subscription.
- Review the list of changes and click Finish.