The Advanced tab of the properties for a group of incremental subscriptions shows the source and destination objects. If you are adding a new group you can select which source and destination object to use. For an existing group of incremental subscriptions you cannot change the source or destination objects.
The Database and Schema for the source and destination are also displayed. The Database field will be blank if not applicable for the DBMS type e.g. Db2 for i or Oracle.
For the Polling Interval specify a numeric value and a frequency (Seconds, Minutes, or Hours) to define how often the Data Replicator should poll for changes at the source. The default polling interval is 3 minutes.
The Error Retry limit specifies how many consecutive errors can occur when polling the source before the Replicator Service pauses the group. Specify 0 (zero) for the limit if you want polling to continue regardless of how many errors are encountered.
Automatic Snapshot check box specifies whether or not to run a baseline when needed. This replaces the choice of As Needed or On Demand on the Schedule page in SQDR prior to v5.10.
The option Receive Change Data Notifications from Capture Agent has been removed from this dialog in SQDR 5.10 & later; this feature is now configured only on the Advanced Dialog of the source (see Source Properties: Advanced tab).
The Apply section contains settings related to applying changes to the target database in an incremental replication.
DML Replication offers the following choices:
Batch: (default) instructs SQDR to apply by destination table order for a given set of transactions.
Merge: use SQL Merge function (if supported by the destination DBMS and by SQDR). As of SQDR 6.11, SQL Server, Snowflake, and PostgreSQL v15 are supported. Note that SQDR Plus must also be at a compatible level of 6.11. The following parameters are related to Merge support:
Merge In place: use the destination database to build the temp merge table
Decoration: specify the suffix to append to the destination table name to contain the merge source changes. If not specified, the default is _M.
Sequence:
If you need to support Foreign Key relationships on the destination
tables (generally not recommended), select this option to enable
Sequenced Apply for scenarios
where the original sequence of DML is required. Some sources such
as SQL Server do not support sequencing regardless of this setting.
Commitment Limits: See Specifying Commit Limits for Incremental Apply for details about commitment limits (Row Limit and Transaction Limit).
DDL Replication, ADD, DROP and MODIFY control how SQDR handles ALTER changes to the source tables. DDL Replication determines when the subscription is run in reaction to a source ALTER, while ADD, DROP and MODIFY (ALTER COLUMN) determine what action is taken. The default values are defined in the Replication tab of SQDR Service Properties. See ALTER Processing for details.
The Change Data Logging section allows you to configure the values used by Apply processing and to specify the name of a stored procedure to process Change Data information instead of, or in addition to, updating a destination table. The stored procedure can reside either in the SQDR control database or the destination database. See Change Data Processing for details.
Logging Level: choose the desired value from the dropdown field:
*DISABLED (default)
Data-Always
Errors-Only
Keys-Always
Encoding: choose the desired value from the dropdown field:
*DEFAULT - use the useXMLEncoding
service property
JSON
XML
Stored Procedure: Enter the name of the stored procedure to be invoked. You may need to qualify the stored procedure e.g. MYSCHEMA.MYPROC. The stored procedure is invoked with the same credentials as used by SQDR to access the control database or destination e.g. sqdr for a Db2 for LUW control database, sa for a SQL Server control database (in this case, you will typically qualify the stored procedure name with dbo), or the userID configured in the Destination for a destination DBMS.
Select the location of the stored procedure to invoke: Control DBMS or Destination DBMS
Parameters: Selecting this button will bring up a dialog where you can enter or paste the parameters to be supplied to the stored procedure. For instance, if you are using the SQDR v5 Kafka Producer (TOKAFKA stored procedure), you would enter the properties for the Kafka connection and (optionally) the Topic, with each property on a separate line.
For SQDR v6 Streaming Support and Data Sink support (i.e. where you have configured Stream (Using Apply extensions) on the Advanced panel of the Destination), only the Parameters button and Before Image included setting are used; you can ignore the rest of the Change Data Logging section.
The parameters configured here for SQDR v6 may include:
The className of the desired Apply extension e.g.
className=com.starquest.sqdr.apply.kafka.KafkaSparkProcessor
className=com.starquest.sqdr.apply.ApplyPullProcessor
boostrap.servers (Kafka connection properties) if using Kafka
topic
batch.size
linger.ms
Before Image included determines how the Before Image information is delivered:
*Default: Use the value defined in the Change Data Logging Defaults section of the Replication tab of the SQDR Service properties.
Separately (behavior of SQDR prior to v5.08): the Before Image is a separately logged row.
Combined: the Before Image is appended to the After Image data.
Note: to deliver a Before Image, the subscription must be configured as Archive all DML Activity or must include a criteria (even if the criteria is defined as 1=1, which delivers all rows).
Before Image is available from the following source DBMS platforms
Db2 for i (for tables journaled as *BOTH)
Oracle
SQL Server (CDC - Change Data Capture - only)
Db2 for LUW
MySQL
The Subscription Wizard Apply Defaults control the default value of certain advanced settings on the destination dialog for newly created subscriptions; see I/R Subscription Options for details.