Microsoft Azure Synapse SQL Connector

Back Next

General rules and guidelines

Applicable object types, transformations, and fields: The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:; Transformations
Object type

Source
Single object, multiple objects, query

Lookup
Single object, query
Applicable for unconnected, and connected cached and uncached.

Target
Single object

Advanced fields such as the schema and table name are supported for the Source, Lookup, and Target transformations.
Multiple sources: Consider the following guidelines:
If the mapping contains multiple sources, you can override the schema in the advanced properties only if the schema selected in the source objects is the same, as in the following example:
object1:
schema1.object1

object2:
schema1.object2

If the schema is different, for example, if the schema for object1 is
schema1.object1
and object2 is
schema2.object2
, migration does not work.
Do not override the table from the advanced properties if the mapping contains multiple objects.
Advanced filter and table name override combination: If the mapping contains an advanced filter for the object, for example, <Table2>, in the query options section and an override to the table name in the advanced properties, consider the following rules to override the table:
In mappings, consider one of the following options:
The advanced filter in the mapping must include the
$$Filtercondition
value. In the mapping task, you can override the value from the parameter file in the task properties. The parameter condition in the parameter file must include the following condition:
$$Filtercondition =<Table2>.id >= 1

Use the table name that you specify as an override in the advanced properties directly in the advanced filter condition. For example,
<Table2>.id >= 1

When you create mappings in advanced mode, use the table name specified as an override in the advanced properties directly in the advanced filter condition. For example,
<Table2>.id >= 1
SQL override: In the mapping, do not specify an SQL override when the object type is a single object. A mapping with this combination fails.
Table name override: In the mapping, do not specify a table name override when the object type is a custom query. A mapping with this combination fails.
Schema change handling: You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides, as schema change handling is not applicable.
Update override: When you write data to Microsoft Azure Synapse SQL and specify an update override for the target object, after you migrate the mapping, ensure that the target object specified in the override exists in the mapping.

Transformations	Object type
Source	Single object, multiple objects, query
Lookup	Single object, query Applicable for unconnected, and connected cached and uncached.
Target	Single object
Advanced fields such as the schema and table name are supported for the Source, Lookup, and Target transformations.

Rename Saved Search

Table of Contents

Microsoft Azure Synapse SQL Connector

Microsoft Azure Synapse SQL Connector

General rules and guidelines

General rules and guidelines