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

Rules and guidelines for dynamic schema handling

Rules and guidelines for dynamic schema handling

Consider the following rules and guidelines when you enable dynamic schema change handling:
Mappings
  • When you enable dynamic schema change handling, you cannot make changes to the columns of Uniqueidentifier data type.
  • When you read data from or write data to a Microsoft Azure Synapse SQL and override the schema name or table name, do not use the
    Alter and apply changes
    or
    Drop current and recreate
    option.
  • When you alter the datetime data type to another, Data Integration always maps the altered field to the
    datetime
    field in the Microsoft Azure Synapse SQL target.
    For example, if you alter the source
    datetime
    field to
    datetime2
    , Data Integration maps the
    datetime2
    field to
    datetime
    in the Microsoft Azure Synapse SQL target.
  • When you read data from Microsoft Azure Synapse SQL, any table or column constraints in the source table are not retained in the target.
Mappings in advanced mode
  • You cannot use schema change handling when you use a custom query as the source type.
  • When you use the
    Drop current and recreate
    option, special characters in the column name are written as underscore in the target.

0 COMMENTS

We’d like to hear from you!