Greenplum as Target

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

• HVR uses the DataDirect Connect XE ODBC driver to write data into Greenplum during Continuous Integrate and Row-wise Refresh.
• By default, HVR writes data into Greenplum 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 Greenplum.

HVR's internal tables like burst and state-tables will be created in schema public.

Grants for Integrate, Refresh, and Compare

This section lists the grants required for comparing or integrating (Integrate and Refresh) changes into Greenplum.

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

  grant connect, create on database dbname to username;
  
  grant select, insert, update, delete on table replicated_table_name to username;
  

• The HVR database User must be granted the following privilege to change tables which are in another schema (using action TableProperties with parameter Schema):

  grant usage on myschema to username;
  

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

  grant create on myschema to username;
  

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.