Table of Contents

Search

  1. Preface
  2. Introduction to Microsoft Azure Synapse SQL Connector
  3. Connections for Microsoft Azure Synapse SQL
  4. Mappings for Microsoft Azure Synapse SQL
  5. Upgrading to Microsoft Azure Synapse SQL Connector
  6. Migrating a mapping
  7. SQL ELT optimization
  8. Data type reference
  9. Troubleshooting

Microsoft Azure Synapse SQL Connector

Microsoft Azure Synapse SQL Connector

Use a different object path for the migrated mapping

Use a different object path for the migrated mapping

After you migrate the mapping, you can use a different object path to run the mapping from the new environment. In this scenario, before you migrate the mapping, you can change the object metadata, runtime attributes, or the connection attributes to reflect the object path in the migrated environment. You do not have to edit or update the mapping in the new environment.
As a rule, when you specify the schema or table in the advanced properties, connection, or object properties, Data Integration honors the attributes in the following order of precedence:
  1. Runtime advanced attribute
    s. The advanced properties such as schema and table in the Source, Target, or Lookup transformation in a mapping.
  2. Connection attributes
    . Attributes such as database and schema set in the connection properties.
  3. Object metadata
    . The object selected in the Source, Target, or Lookup transformation in a mapping.
When you migrate a mapping, ensure that the metadata of the imported object matches the metadata fetched in an override.

0 COMMENTS

We’d like to hear from you!