Guidelines to migrate to Microsoft Azure Synapse SQL
Guidelines to migrate to Microsoft Azure Synapse SQL
Some guidelines and restrictions apply to assets when you migrate the Microsoft Azure SQL Data Warehouse V1 and V2 connections to Microsoft Azure Synapse SQL.
Guidelines applicable to Microsoft Azure SQL Data Warehouse V1 connection
The following guidelines are applicable when you migrate the Microsoft Azure SQL Data Warehouse V1 connection to Microsoft Azure Synapse SQL.
Source transformation
Consider the following migration guidelines when you configure a read operation:
After the migration, when you run a mapping to read data that contains special characters, the mapping fails with the following error:
[FATAL] Exception occured while validating record metadata: ______________________________1 is invalid field name.
To avoid this error, after the migration, refresh the metadata or regenerate the fields and run the mapping again.
After the migration, when you run a mapping to read data that contains unicode characters, the mapping fails with the following error:
[ERROR] Invalid operation field name in CCI Metadata Client.
To avoid this error, after the migration, refresh the metadata or regenerate the fields and run the mapping again.
Target transformation
After the migration, when you configure a Target transformation, the Success File Directory and Error File Directory target properties are not available in Microsoft Azure Synapse SQL.
Guidelines applicable to Microsoft Azure SQL Data Warehouse V2 connection
When you configure any operation other than insert, and then migrate to Microsoft Azure Synapse SQL, you must select the applicable target attribute
Treat Source Row As
in the Microsoft Azure Synapse SQL target properties before you run the mapping.
Guidelines applicable to Microsoft Azure SQL Data Warehouse V1 and V2 connection
The following guidelines are applicable when you migrate the Microsoft Azure SQL Data Warehouse V1 and V2 connections to Microsoft Azure Synapse SQL.
Parameterization
Consider the following migration guidelines when you parameterize Microsoft Azure SQL Data Warehouse mappings:
If you create a completely parameterized mapping, do not specify the connection type in the connection parameterization. If you specify the connection type in the connection parameterization and then perform the migration, the mapping fails at runtime.
When you parameterize both the connection and the objects in a Microsoft Azure SQL Data Warehouse V1 and V2 mapping, the data preview in the mapping task might fail after the migration with the following error:
Internal error while processing request. Please contact Informatica Global Customer Support.
To avoid this error, reselect the object in the mapping to preview the data.