Azure Synapse as a source
To provide the information SnapLogic AutoSync needs to connect to Azure Synapse, supply new credentials in the wizard or select saved credentials. AutoSync requires a Binary Large Object (BLOB) staging area for Azure Synapse.
To use the Incremental load type, you'll need to select a column that contains the last updated timestamp for each table.
Tables selected for Incremental or SCD2 load must meet the following requirements:
- Have a primary key column.
- Unless the environment is configured to relax this requirement, the column that tracks the last update time can't be nullable or contain null values.
The last modified column must be
one of the following types:
datetime
datetime2
datetimeoffset
smalldatetime
Supported Snap account types
Designer and Classic Manager provide multiple Snap account types for most endpoints and not all types are compatible with AutoSync. When you create or edit a data pipeline, the existing credentials list includes only compatible accounts.
Many Snap accounts support references to JAR files. If you create an account that references a JAR file for use in AutoSync, you must use an absolute path to the JAR file.
For Azure Synapse, AutoSync supports:
- Azure Synapse SQL Account
Azure Synapse as both source and target
- When loading data from an Azure Synapse source to an Azure Synapse destination, the source schema must be different than the destination schema.
- When using Azure Synapse as both a source and a target, the loaded data for some columns might be a different data type than they were in the source. This is because AutoSync maps data through a common data model.
Connection configuration
Azure Synapse properties include the following:
- Account Properties
- Credential label: A unique, meaningful name such as
Azure-Synapse-Sales
. If a configuration with the same name exists, AutoSync displays anAsset conflict error message
. - Hostname: The URL for Synapse, such as
organization-synapse.sql.azuresynapse.net
- Port Number: The Synapse port number. The default is
1433
. - Database name: The Synapse database name. For example,
Sales-DB
- Username: The username for an account with the correct permissions to write data. For example
Sales-admin
. - Password: The password for the account. Multiple retries with an invalid password can cause your account to be locked.
- External Storage Endpoint: The storage URL, in the following format: Blob storage:
.blob.core.windows.net
- Storage Account: The Azure storage account name.
- Azure Container: The container name.
- Azure Folder: The folder name.
- Azure Auth Type: The type of authorization AutoSync should use for the account, Access Key, Shared Access Signature, or Managed Identity.
- Azure Identity: The managed identity for Azure authorization. Required for all three types of authorization.
- Azure Access Key: The key Azure generated for the account. Required for Access Key and Shared Access Signature authorization.
- Share: (Optional) Select a user group to share this configuration with. Org admins create user groups to share credentials. If you are a member of a user group, you can select it from the dropdown. You can also select the global shared folder, which shares the credentials with everyone in your Org.
- Credential label: A unique, meaningful name such as
- Validate and save: After saving, AutoSync adds the configuration to the list of saved credentials.
- Select schema: AutoSync populates this list from the account. Choose the schema to use as the destination.
- Select a table to synchronize: Choose a table to synchronize. AutoSync populates the list from your Azure Synapse account. For incremental load, select a column that tracks the last update.
- Select the column that tracks the last modified time: To use Incremental or SCD2 load, select a column that tracks modifications. To use Full load, leave this field empty. Refer to Incremental load for more information.