Used to load data to and from Azure Synapse SQL.
This connection type supports the following task types:
This connection can be used in a Data Migration.
| Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
|---|---|---|---|
| ✔ | ✔ | ✔ | ✔ |
| Template Name | Description |
|---|---|
| Azure Synapse SQL | The standard connection string for connecting to an Azure Synapse SQL instance. |
You can copy the connection string template below into the connection string field in Loome Monitor and then replace the placeholders with your own details.
| Template | Example |
|---|---|
Server=YOUR_SERVER,1433;Initial Catalog=YOUR_DATABASE_NAME;Persist Security Info=False;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30; |
Server=tcp:loome-sample-synapse.sql.azuresynapse.net,1433;Initial Catalog=Loome-Sample;Persist Security Info=False;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30; |
You can use the ‘Copy’ function of Azure Synapse by selecting Enable Azure Copy to choose an Azure blob storage connection. You can use Azure Synapse’s copy function for data migration and persistent staging tasks, but not in incremental data migrations.
When using the copy function, you have the option to use a CSV or Parquet staging type. We recommended that you use CSV unless storage size is an issue in your Azure storage location.
In Azure or Snowflake, the flat file created will still include columns that were ignored. These columns will be null and ignored in the final target database.
The copy in Azure Blob Storage will remain in your blob storage as Loome does not remove it once copied. The copy will be overwritten if the task is re-run, Azure Copy is enabled and the data table uses the same name, but Loome Integrate will not remove any files from your blob storage.
You can learn more about file definitions and Parquet here.