Release Notes

Migrate data and replicate changes to Exasol database. Exasol is an in-memory relational database built for high performance analytics. Even though it was designed to run in memory, it persists data to disk following ACID rules and follows SQL query standards. Support for Exasol makes it a compelling data migration target for building a data warehouse.

Enables the use of the Sybase ASE bulk copy program utility (bcp) for extracting initial load. See also parameters that will configure bcp out: ase.bulk.load.bcp.cmd, ase.bulk.load.field.terminator, and ase.bulk.load.row.terminator. (Default: false)

Specifies the path to the Sybase ASE bulk copy program utility (bcp) executable. (Default: )

Specify the field terminator used by the Sybase ASE bulk loader. Pick something that does not exist in the data in your database. (Default: |})

Specify the line terminator used by the Sybase ASE bulk loader. Pick something that does not exist in the data in your database. (Default: |>\n)

If this is true, when a delete affects zero rows, if the table is configured for sync on incoming, then the auto resolver will write the deletes into the capture log. (Default: false)

Enables the target to bulk load (bcp in) a data file that is located in the source staging (from bcp out), when both source and target are on the same server. (Default: true)

Maximum number of bytes to write to file before loading data via a bulk loader (Default: 1000000000)

This is the amount of time ready queue entries will be cached before re-reading them from the database. (Default: 5000)

The authorization endpoint is used by SymmetricDS in order to interact with your OAuth 2.0/OIDC provider and get the authorization to access the protected resource. (Default: )

This is the Client ID that your OAuth 2.0 provider gives you when you create your OAuth 2.0 Credentials. (Default: )

This is the Client secret that your OAuth 2.0 provider gives you when you create your OAuth 2.0 Credentials. (Default: )

URL of the OpenID Provider’s JWK Set document. This contains the signing key(s) SymmetricDS uses to validate signatures from the OpenID Provider. (Default: )

The issuer identifier of the OpenID Provider. (Default: )

Map of OAuth 2.0/OIDC roles to console role IDs. Allows OAuth 2.0/OIDC users to log in without having a corresponding console user if they are assigned one of the specified roles. (Default: )

The token endpoint is used by SymmetricDS in order to get an access token or a refresh token from your OAuth 2.0/OIDC provider. (Default: )

Metadata endpoint info of the SAML IdP. When set, SymmetricDS will obtain the public x509 certificate(s) from this URL. (Default: )

Path to a file containing properties for the OneLogin SAML Java Toolkit that SymmetricDS uses behind the scenes. The values in this file will override any default values built into SymmetricDS or the Toolkit, but not any values set by parameters. (Default: )

Number of days that the SAML SP certificate will last before it expires. Values below 1 are invalid and will be changed to 25 years. (Default: 9125)

Maximum number of days before the SAML SP certificate expires when the Purge Incoming job will replace it with a new certificate. (Default: 30)

If set to true, when a table’s schema is sent to the target database it will also send the DDL script that will create an application trigger at the target if the source and the target database types are the same. SymmetricDS trigger DDL statements will not be sent. (Default: false)

Enables removal of block comments from script text by data loader processing DDLs. Applies to stores procedures and functions, when DDL replication is enabled. (Default: true)

If source and target engine are hosted together, the source will send a "retry" command instead of sending the batch, and the target will use the source’s outgoing staging to access the batch. This also requires the staging to be enabled (stream.to.file.enabled=true). (Default: true)

If tables are created as part of the initial load, it will defer setting up table-level logging to improve performance. Applies to loads only. After data is loaded, the table-level logging will be switched on. This parameter needs set for the node that will send the initial load, not the node receiving it. Support for table-level logging varies by database dialect and is ignored where not applicable. Currently this is only supported by the PostgreSQL UNLOGGED feature. Oracle’s NOLOGGING feature might be implemented in the future. Note: this parameter is not compatible with PostgreSQL tables referenced by foreign keys. (Default: false)

The number of milliseconds that the initial load extract job can run a thread for processing extracting requests. (Default: 3600000)

The number of threads available for concurrent push/pulls of initial load batches using the reload queue. If the reload channel is placed on its own reload queue, multiple threads are created for push/pulls using dynamic queues named internally as reload!0, reload!1, reload!2, etc. Dynamic queues have the advantage of processing a table on the next available queue, preventing one queue from being full while other queues are empty. (Default: 20)

Whether to use all available threads for an initial load on the reload queue. Set to "true" to use all available threads, or "false" to use one thread. Set to "auto" and it will use all available threads only if the load is deferring constraints. (Default: auto)

Enables the use of the SQL Server bulk copy program utility (bcp) for extracting initial load. See also parameters that will configure bcp out: ase.bulk.load.bcp.cmd, ase.bulk.load.field.terminator, and ase.bulk.load.row.terminator. (Default: false)

Specifies the code page to pass to the bcp process using the -C command line option. This parameter only applies to the bcp process running on Windows. (Default: )

Enable this parameter to activate binary mode for PostgreSQL bulk loader utilizing the COPY IN statements. If a column type unsupported by the binary mode is encountered batch will be switches to the text mode. (Default: false)

Whether push and pull should use ready queues to limit queries and communication. Ready queues is the list of queues with outgoing batches that are ready to be sent, queried periodically and cached. When enabled, the pull service first pulls the default queue and receives a list of ready queues that should also be pulled, instead of pulling those queues every time. The push service gets the list of ready queues to allocate threads for calling data extractor service. (Default: true)

Specifies if server cert should be trusted when connecting bcp bulk loader to SQL Server. Applies to Linux and macOS only. (Old Default: false) (New Default: true)

Enables the use of the SQL Server bulk copy program utility (bcp) as the bulk loader. (Old Default: false) (New Default: true)

When sending an outgoing batch, copy directly from the outgoing staging to the incoming staging when both nodes are on the same server. This also requires the staging to be enabled (stream.to.file.enabled=true). The HTTP transport is still used to send a batch "retry" instruction that causes the target node to read from staging. Deprecated and replaced by incoming.batches.use.source.staging. (Old Default: true) (New Default: false)

When enabled, use a thread per channel for parallel routing. (Old Default: false) (New Default: true)

{REMOVED}

{REMOVED}

{REMOVED}

{REMOVED}

{REMOVED}