MySQL as Target

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

• By default, HVR writes data into MySQL using Continuous Integrate and Row-wise Refresh. HVR uses MariaDB's native Connector/C interface to write data into MySQL during Continuous Integrate and Row-wise Refresh.
• You can also use Burst Integrate and Bulk Refresh for writing data into MySQL. 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 MySQL.

In MySQL bi-directional channel, Bulk Refresh may result in looping truncates on either side of the bi-directional channel. For a workaround, see section MySQL Bi-directional Replication.

Grants for Integrate and Refresh

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

• The HVR database User must be granted the select, insert, update, and delete privileges to read and change replicated tables.

  grant select, insert, update, delete on tbl to username
  

• The HVR database User must be granted permission to create and drop the HVR state tables.

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.