Capabilities for Azure Synapse Analytics

This section lists the Capabilities of Fivetran HVR when using 'Azure Synapse Analytics'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Azure Synapse Analytics Requirements.

Capture

HVR does not support Capture changes from location on Azure Synapse Analytics.

Repository Database

HVR does not support Repository database on Azure Synapse Analytics.

Integrate

HVR supports the following capabilities on Azure Synapse Analytics:

• Integrate changes into location.
• Burst integration (Integrate with parameter Method=BURST).
• Integrate with parameter BurstCommitFrequency.
• Continuous integration (Integrate with parameter Method=CONTINUOUS).
• ColumnProperties with parameter SoftDelete.
• Creation and update of HVR state tables.

HVR does not support the following capabilities on Azure Synapse Analytics:

• Tables without a key and without TableProperties with NoDuplicateRows for continuous integration.
• Continuous integrate with parameter OnErrorSaveFailed.
• Disable/enable database triggers during integrate (with parameter NoTriggerFiring).
• Integrate with parameter DbProc.

Bi-directional Replication

HVR does not support Bi-directional Replication on Azure Synapse Analytics.

Refresh and Compare

HVR supports the following capabilities on Azure Synapse Analytics:

• hvrrefresh or hvrcompare from source location.
• hvrrefresh into target location.
• Row-wise hvrrefresh into target location (option -g).

HVR does not support the following capabilities on Azure Synapse Analytics:

• Bulk load of multiple slices of same table can be done in parallel.

Other Capabilities

HVR supports the following capabilities on Azure Synapse Analytics:

• Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey).
• International table and column names where DBMS is not configured with UTF-8 encoding.
• Always treat DBMS table names and column names as case sensitive, even if not configured (equivalent to location property Case_Sensitive_Names always set to TRUE) .
• Always treat DBMS schema names case sensitive.