Yes, a table can replicate in Change History manner as well as in full replication manner, so long as it is replicating to two different target tables. As an example, you can have the following entries in the config file for the same source table replicating to target tables using Change History and full replication, respectively:
datasource: o.sourceSID
.
# a sample entry for table in full replication
OWNER1.TABLE1 OWNER2.TABLE12 target_server_name@o.targetSID
# a sample entry for table in Change History (or CDC) replication
OWNER1.TABLE1 !cdc:OWNER3.TABLE3 target_server_name@c.targetSID
The above will result in a common Export queue on source for both the replication streams, namely the CDC and the full replication:
sp_ctrl>qstatus
Queues Statistics for source_server_name
Name: o.sourceSID (Capture queue)
Number of messages: 0 (Age 0 min; Size 1 mb)
Backlog (messages): 0 (Age 0 min)
Name: source_server_name (Export queue)
Number of messages: 4 (Age 0 min; Size 1 mb)
Backlog (messages): 0 (Age 0 min)
However, on the target it will create two separate Post queues, one for full replication and one for the CDC replication:
sp_ctrl>qstatus
Queues Statistics for target_server_name
Name: source_server_name (o. sourceSID -o.targetSID) (Post queue)
Number of messages: 0 (Age 0 min; Size 0 mb)
Backlog (messages): 0 (Age 0 min)
Name: source_server_name (o. sourceSID -c.targetSID) (Post queue)
Number of messages: 0 (Age 0 min; Size 0 mb)
Backlog (messages): 0 (Age 0 min)
© ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center