When you use a custom or saved query in a task and the query contains * instead of a column list, NULL values are returned. You must use a column list instead of * in the query.

When you run a mapping task to create a target, the target is successfully created at runtime. If you drop the created target table and run the task again, the task fails.

When you run a task to update or upsert data in bulk to an Azure SQL Database target, the Secure Agent logs collective statistics of both the update and the insert operations. In normal mode, the Secure Agent logs the statistics of the update and insert operations separately.

When you use a lookup query or lookup SQL override query in a task and the query contains dynamic column names as

?column_name?

, NULL values are returned. To resolve the dynamic column names, provide the query in the

Lookup SQL Override

field and disable the lookup cache.

Consider the following rules and guidelines when you add objects with a hyphen in the column names in the Source and Target transformations:

When the source column name that you read has hyphens and you use the
Create New at Runtime
option to create a target, the hyphens in the table name are converted to underscores in the target column.
When you add a new column to the object in an existing mapping and the column name has a hyphen, you cannot manually add the column in the mapping.
If you parameterize the target object, the manual field map option in the
Field Mapping
tab is not applicable. You must select Automatic, Completely Parameterized, or Partially Parameterized as the field map options for the mapping to work successfully.

You cannot provide in-out parameters in the

Additional Properties

field in a Target transformation.

When you configure a mapping with

SQL ELT optimization

enabled, the Target transformation ignores the

Additional Properties

field.

When a mapping contains multiple targets that share a single connection, the mapping uses the environment SQL value configured in one of the targets. To use different environment SQL values for each target, you need to create a separate connection for each target.