Informatica is fixing a behavior with Azure Synapse connector when using table/schema override properties which causes a change in behavior

 

Am I impacted?

If you use Informatica Azure Synapse connection as a target and use the table/schema override  properties you may encounter the following change in behavior:

  • When you override the target table name or schema name and truncate the target table in Microsoft Azure Synapse SQL, the Secure Agent truncates the table or schema that you specify in the override property before it writes the data to the target. Previously, the Secure Agent truncated the table or schema that you specify at the design time.
  • When you override the target table name or schema name and create a new target at runtime, the Secure Agent creates the target table based on the table name or schema name override that you specify in the advanced properties. Previously, the Secure Agent created the table based on the table name or schema name that you specify at the design time

 

How do I address the issue?

 

  • Validate your mappings that use “Truncate Table” option and verify that the override schema/table values are correct, as the truncate table would now start truncating the overridden object.
  • Create Target would work as expected, if the table doesn't exist it will create, if it exists it will have the same behavior as earlier

 

 

 

Who do I contact if I need help?

If you have any questions, please contact us through Global Customer Support at 1-877-INFAHELP from the US or Worldwide.

 

 

Thank you,

Informatica Team