Skip to main content Skip to complementary content

Setting advanced connection properties

In the Advanced tab, you can set the following properties:

  • Capture DDLs: When this option is selected, the following actions occur:
    • Operational artifacts are created (by Replicate) in the database when the task starts. In order to capture DDL events, Qlik Replicate creates various artifacts in the Amazon RDS for PostgreSQL database when the task starts. You can later remove these artifacts as described in Removing Replicate artifacts from the Amazon RDS for PostgreSQL database.
    • Streamed DDL events are captured.
  • Create DDL artifacts in schema: The schema in which the operational DDL database artifacts will be created. The default value is "Public".
  • WAL heartbeat: An Apply Changes task that is running but not capturing changes (due to source table inactivity) will continue to occupy the LSN position in its replication slot, thereby preventing truncation of the WAL. Since the WAL is a server-wide resource used by all Amazon RDS for PostgreSQL processes, it may grow extremely large if no changes are captured for an extended period.

    To prevent this from happening, enable the "WAL heartbeat" option. When this option is enabled, the Amazon RDS for PostgreSQL source endpoint mimics task activity by periodically committing pseudo transactions (i.e. "Heartbeats") to the heartbeat table, thereby advancing the task slot’s LSN position.

    • Schema for heartbeat artifacts: The schema in which the WAL heartbeat table (attrep_wal_heartbeat) will be created. The default value is "public".
    • Heartbeat frequency (minutes): The frequency with which to commit transactions to the heartbeat table.
  • Map BOOLEAN to Replicate BOOLEAN data type (instead of STRING (5)): Select this option if you want BOOLEAN columns to be mapped to the Replicate BOOLEAN data type instead of STRING (5).

  • Support partitioned tables in CDC: When this option is not selected (the default), in order to capture changes from a partitioned source table, you need to add all of the associated child tables to the task. This will create separate tables on the target for each child table (partition).

    When this option is selected, only the partitioned table needs to be added to the task (without any child tables). In this case, for each partitioned table, a single non-partitioned table will be created on the target .

    Information note
    • Requires PostgreSQL 13 or later
    • UPDATEs to a partitioned source table will be applied as INSERTs and DELETEs to the target table.
    • In homogeneous replication, only the parent table will be created on the target.
    • When this option is selected, the following DDLs are not supported:

      • Drop partition
      • Detach partition
      • Attach partition - with data

Internal parameters

Internal parameters are parameters that are not exposed in the UI. You should only use them if instructed by Qlik Support.

To add internal Qlik Replicate parameters:

  1. Click the Internal Parameters link.

    The Internal Parameters dialog box opens.

  2. In the edit box, type the name of the parameter you need to add and then click it.
  3. The parameter is added to the table below the search box with its default value.
  4. Change the default value as required.
  5. To reset the parameter value to its default, click the "Restore default value" icon at the end of the row.

More options

These options are not exposed in the UI as they are only relevant to specific versions or environments. Consequently, do not set these options unless explicitly instructed to do so by Qlik Support or product documentation.

To set an option, simply copy the option into the Add feature name field and click Add. Then set the value or enable the option according to the instructions you received.

Settings summary

You can view a summary of your settings by clicking the Setting Summary link. This is useful if you need to send a summary of your settings to Qlik Support.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!