Changed behavior

If you use the CDC Tables method to capture change data from SQL Server sources that include persisted computed columns, database ingestion and replication incremental load and combined load jobs now replicate the computed column expression values instead of nulls. If you want to revert to the prior behavior of replicating nulls for persisted computed columns, set the pwx.custom.sslr_cdcread_replicate_persisted_cols custom property to false on the Source page of the task wizard.

For database ingestion and replication incremental load jobs that have SQL Server sources and capture data from CDC tables, which primarily occurs when using the CDC Tables capture method, Database Ingestion and Replication now uses active management of the CDC tables by default. Activate management enables enhanced processing of source DDL and DML changes. Previously, to use active management of CDC tables, you had to set the pwx.custom.sslr_cdc_manage_instances source custom property to true. Now the default value for this property is true.

For database ingestion and replication incremental load jobs that have a SAP HANA source, when a new column is added to the source table and it is not present in the shadow _CDC tables, the new column is ignored.

Previously, when a new column of a supported SAP HANA data type was added to the source table, it was included in the source definition and the job failed because a corresponding column was not found in the shadow _CDC tables. If you want to revert to the prior behavior, set the pwx.cdcreader.HANA.addColIgnore custom property to false on the Source page of the task wizard.

Newly deployed application ingestion and replication jobs and database ingestion and replication jobs that use the Avro output format now map source types to the Avro logical types of date, decimal, and timestamp (with microsecond precision) by default. For jobs that have already been deployed or that are redeployed, the prior behavior of mapping all source types to the Avro primitive type of string by default continues. The change to using Avro logical types helps downstream applications and processes process the Avro data correctly. If you want to revert to the prior behavior, you can set the custom property avroEnableLogicalTypes to false on the Target page of the task wizard.