Capabilities for Teradata

This section lists the Capabilities of HVR when using 'Teradata'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for Teradata.

Capture

HVR does not support Capture changes from location on Teradata.

Hub Database

HVR supports Hub database on Teradata.

Integrate

HVR supports the following capabilities on Teradata:

• Integrate changes into location (Teradata from version 14.00 to version 17.00).
• Integrate with /Burst (Teradata from version 14.00 to version 17.00).
• Integrate with /BurstCommitFrequency (Teradata from version 14.00 to version 17.00).
• Continuous integration (Integrate without /Burst) (Teradata from version 14.00 to version 17.00).
• Action Transform /SoftDelete (Teradata from version 14.00 to version 17.00).
• Creation and update of HVR state tables (Teradata from version 13.10 to version 17.00).

HVR does not support the following capabilities on Teradata:

• Action TableProperties with /DuplicateRows for continuous integration.
• Continuous Integrate with /OnErrorSaveFailed (without /Burst).
• Disable/enable database triggers during Integrate (/NoTriggerFiring).
• Integrate with /DbProc.

Bi-directional Replication

HVR does not support Bi-directional Replication on Teradata.

Refresh and Compare

HVR supports the following capabilities on Teradata:

• Hvrrefresh or Hvrcompare from source location (Teradata from version 13.10 to version 17.00).
• Hvrrefresh into target location (Teradata from version 13.10 to version 17.00).
• Row-wise Hvrrefresh into target location (option -g) (Teradata from version 13.10 to version 17.00).

Other Capabilities

HVR supports the following capabilities on Teradata:

• Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey) (Teradata from version 13.10 to version 17.00).
• Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (Teradata from version 14.00 to version 17.00).
• International table and column names where DBMS is not configured with UTF-8 encoding (Teradata from version 13.10 to version 17.00).
• Treat DBMS table names and columns as case sensitive if configured (action LocationProperties /CaseSensitiveNames defined) (Teradata from version 13.10 to version 17.00, since HVR 5.6.5/1).

HVR does not support the following capabilities on Teradata:

• Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10).