Snowflake as Target

Fivetran HVR supports integrating changes into Snowflake location. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into Snowflake location. For the list of supported Snowflake versions into which HVR can integrate changes, see Integrate changes into location in Capabilities.

HVR uses the Snowflake ODBC driver to write data into Snowflake during Continuous Integrate and Row-wise Refresh.

The preferred methods for writing data into Snowflake are using Burst Integrate and Bulk Refresh as they provide better performance. However, it is required to create staging files on a temporary location to perform Burst Integrate and Bulk Refresh. For more information about staging, see section Staging for Snowflake.

Due to technical limitations, external staging on Azure for Snowflake is not supported in the HVR releases since 6.1.5/3 to 6.1.5/9.

Grants for Integrate and Refresh

This section lists the grants required for integrating changes into Snowflake.

• The user (Role) should have permission to read and change replicated tables.

  grant all privileges on future tables in database databasename to role rolename;
  
  grant select, insert, update, delete, truncate on future tables in database databasename to role rolename;
  

• The user (Role) should have permission to create and drop HVR state tables.

• The user (Role) should have permission to create and drop tables when Refresh will be used to create target tables.

  grant usage, modify, create table on schema schemaname in database databasename to role rolename;
  

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.