Capabilities for Teradata

From HVR
Jump to: navigation, search

This section describes the capabilities supported by HVR on Teradata. For more information about the requirements, access privileges, and other features of HVR when using Aurora MySQL for replication, see Requirements for Teradata.

Capture

HVR does not support Capture changes from location on Teradata


HVR Hub

HVR supports Hub database (Teradata version 14.00 and above)


Integrate

HVR supports the following capabilities on Teradata:

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


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:


Other Capabilities

HVR supports the following capabilities on Teradata:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey)
  • Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (Teradata version 14.00 and above)


HVR does not support the following capabilities on Teradata:

  • International table and column names where DBMS is not configured with UTF-8 encoding
  • Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10)