Teradata as Target

Fivetran HVR supports integrating changes into Teradata location. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into Teradata location. For the list of supported Teradata versions, into which HVR can integrate changes, see Integrate changes into location in Capabilities. HVR also allows you to perform Compare for Teradata database in source location.

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

HVR uses the TPT Load interface for copying data into the Teradata tables during Bulk Refresh and the TPT Stream/Upload interface for loading data into the burst table during Burst Integrate.

The preferred methods for writing data to Teradata are using Burst Integrate and Bulk Refresh as they provide better performance.

Grants for Integrate and Refresh

This section lists the grants required for integrating changes into Teradata. By default, the HVR User has all required permissions to Integrate changes into default user database.

To create target tables using Refresh, the HVR database User must be granted create table and drop table privileges.
```
grant create table, drop table on targetdb to username;
```
To change tables that are owned by other users (using action TableProperties with parameter Schema), the HVR database User must be granted select, insert, update, and delete privileges.
```
grant select, insert, update, delete on targetdb to username;
```
To perform Burst Integrate and Bulk Refresh, the HVR database User must be granted create macro and drop macro privileges.
```
grant create macro, drop macro on targetdb 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.