The July 2025 release includes changes in behavior for the following connectors.
Microsoft Azure Synapse SQL Connector
Effective in this release, when you read data from Microsoft Azure Synapse SQL and the source table uses a UTF-8 compatible collation, you can read data directly from Microsoft Azure Synapse SQL without staging the data.
Previously, if the source table used a UTF-8 compatible collation, the mapping failed as it used Polybase queries that do not support UTF-8 collations.
Microsoft Fabric Data Warehouse Connector
Effective in this release, when you create a Microsoft Fabric Data Warehouse target at runtime where incoming string fields have a precision greater than 4000, the mapping preserves the precision in the new target.
Previously, the mapping did not preserve the precision of the incoming field and set the precision to 8000 by default.
Snowflake Data Cloud Connector
Effective in this release, Snowflake Data Cloud Connector includes the following changes in behavior:
•A Snowflake mapping rolls back the partial data written to the target and fails with an error message in the session log when all the following scenarios are true:
- The mapping writes to a Snowflake target.
- The target is configured with the onError=ABORT_STATEMENT and oneBatch=true load properties in the Additional Write Runtime Parameters field in the Target transformation.
- A transformation in the mapping pipeline fails.
Previously, the mapping failed without an error message and wrote the partial data to the Snowflake target.
If you want to retain the previous behavior, set the -DSNOWFLAKE_ENABLE_TARGET_ROLLBACK_ON_ERROR JVM option property value to false in the Secure Agent properties.
•When you run a mapping that writes a large record with the binary fields of high precision and optimize the write operation by setting the INFA_DTM_STAGING_ENABLED_CONNECTORS staging property in the Secure Agent properties, the mapping creates a single staging file that contains the binary fields.
Previously, the mapping created multiple staging files for the binary fields of high precision.
If you want to retain the previous behavior, set the DTMDisablePartialEORStagingSupport custom property value to yes in the Secure Agent properties.