When you rerun a mapping task that was enabled to create a new target at runtime, even though you drop the target table and make no changes to the mapping, the task runs successfully, but the data types are inconsistent in the target. (February 2021)

When you join multiple tables where the length of the table name is 63 bytes or more, the mapping fails. (February 2021)

When you parameterize multiple JDBC V2 objects, the query generated results in an error. (February 2021)

When you join multiple Azure SQL Database tables from two different schemas that have the same table name, the mapping fails. (October 2020)

When you run a mapping enabled with the

Create New at Runtime

option to write to an Azure SQL Database target and the input data contains the Image or Varbinary(max) data types, the mapping fails with the following error:

String or binary data is truncated

When you run a mapping enabled with the

Create New at Runtime

option to write to an Azure SQL Database target, Unicode characters from the source are replaced with ? in the target table. (October 2020)

When you run a mapping enabled to create a new PostgreSQL target at runtime and the source data contains the Time data type, the mapping runs successfully but the Time value in microseconds is truncated to milliseconds. (October 2020)

When you configure a mapping enabled to create a new Azure SQL Database target at runtime and the input data contains the Float, Double, or Real data types, the mapping fails. (October 2020)

When you import JDBC V2 source objects where the table and column names contain special characters, the mapping fails. (October 2020)