Azure Synapse Analytics as Target

Fivetran HVR supports integrating changes into Azure Synapse location. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into Azure Synapse location.

HVR uses the following interfaces to write data into an SQL Server location:

• SQL Server ODBC driver, used to perform Continuous Integrate and Row-wise Refresh.
• SQL Server BCP interface, used for copying data into database tables during Burst Integrate and Bulk Refresh.

Grants for Compare, Refresh and Integrate

This section lists the grants required for integrating changes into Azure Synapse.

• The HVR database User must be granted the following privileges:

  grant create table to username;
  
  grant select, insert, update, delete on replicated tables to username;
  

• To perform Bulk Refresh or alter tables which are in another schema (using action TableProperties with parameter Schema=myschema), the HVR database User must be granted the following privilege:

  grant control on schema :: myschema to username;
  

• When Refresh is used to create the target tables, the HVR database User must be granted the following privilege:

  grant create table on schema :: myschema to username;
  

HVR's internal tables, like burst and state-tables will be created in the user's default_schema. The default_schema can be changed using:

alter user hvr_user with default_schema = myschema;

Intermediate Directory

This option in the HVR UI allows you to specify a directory path for storing intermediate (temporary) files generated during Compare. These files are created during both "direct file compare" and "online compare" operations.

Using an intermediate directory can enhance performance by ensuring that temporary files are stored in a location optimized for the system's data processing needs.

This setting is particularly relevant for target file locations, as it determines where the intermediate files are placed during the Compare operation. If this option is not enabled, the intermediate files are stored by default in the integratedir/_hvr_intermediate directory, where integratedir is the replication DIRECTORY (File_Path) defined for the target file location.

This option is equivalent to the location property Intermediate_Directory.

Intermediate Directory is Local

This option in HVR UI specifies that the Intermediate Directory will be created on the local drive of the file location's server.

This setting is crucial for optimizing performance, as it reduces network latency and avoids potential permission issues associated with remote storage. By storing intermediate files locally, HVR can process data more efficiently, taking advantage of the speed and reliability of local storage.

This option is particularly beneficial when the HVR Agent has access to ample local storage, enabling it to handle large data volumes without relying on networked storage solutions.

This option is equivalent to the location property Intermediate_Directory_Is_Local.