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 mappings in advanced mode

Rules and guidelines for mappings in advanced mode

Consider the following rules and guidelines when you create mappings in advanced mode:
  • When you configure a Sequence transformation in a mapping in advanced mode, the mapping fails.
  • When you create a connection and specify an incorrect value for an Azure storage-specific connection property, the test connection is successful. However, the mapping in advanced mode fails with the following exception:
    Caused by: org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: One of the request inputs is not valid
    Ensure that you specify valid storage parameters when you configure the connection.
  • When you select Microsoft Azure Data Lake Storage Gen2 as the storage type for both source and target connections, ensure that you use the same access key for both the source and target connections.
    For example, if you use Key 1 as the access key for the source connection and Key 2 for the target connection, the mapping fails.
  • You cannot use system assigned identity for mappings in advanced mode.
  • You cannot add multiple pipelines in a mapping.
  • When you specify the external data source in the connection properties, you must specify the container or file system used to create the external data source either in the connection properties or in the advanced properties.
  • When you run a mapping in advanced mode and map the source fields of double or float data type to the target fields of string data type, the format of the values changes in the target.
    The following table describes the change in the format of the values in the target:
    Value in the source
    Value in the target
    1.7976931348623157e+308
    1.79769313486232e+308
    -9999999999999.99
    -10000000000000
    4.94065645841247e-324
    4.9e-324
    7956318123.99392483
    7956318123.99392
  • When you run a mapping in advanced mode to write float or real data types, the source data and target data don't match in some cases. The values written to the target are approximate and not the same as in the source. To write the exact values, map real and float data types with numeric or decimal data types.

0 COMMENTS

We’d like to hear from you!