Capabilities for Teradata
This section lists the Capabilities of Fivetran HVR when using 'Teradata'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Teradata Requirements.
Capture
HVR does not support Capture changes from location on Teradata.
Repository Database
HVR does not support Repository database on Teradata.
Integrate
HVR supports the following capabilities on Teradata:
- Integrate changes into location (Teradata from version 16.00 to version 17.00).
- Burst integration (Integrate with parameter Method=BURST) (Teradata from version 16.00 to version 17.00).
- Integrate with parameter BurstCommitFrequency (Teradata from version 16.00 to version 17.00).
- Continuous integration (Integrate with parameter Method=CONTINUOUS) (Teradata from version 16.00 to version 17.00).
- ColumnProperties with parameter SoftDelete (Teradata from version 16.00 to version 17.00).
- Creation and update of HVR state tables (Teradata from version 16.00 to version 17.00).
HVR does not support the following capabilities on Teradata:
- Tables without a key and without TableProperties with NoDuplicateRows for continuous integration.
- Continuous integrate with parameter OnErrorSaveFailed.
- Disable/enable database triggers during integrate (with parameter NoTriggerFiring).
- Integrate with parameter 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 16.00 to version 17.00).
- hvrrefresh into target location (Teradata from version 16.00 to version 17.00).
- Row-wise hvrrefresh into target location (option -g) (Teradata from version 16.00 to version 17.00).
HVR does not support the following capabilities on Teradata:
- Bulk load of multiple slices of same table can be done in parallel.
Other Capabilities
HVR supports the following capabilities on Teradata:
- Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey) (Teradata from version 16.00 to version 17.00).
- Call database procedure dbproc during replication jobs (AgentPlugin with parameter DbProc) (Teradata from version 16.00 to version 17.00).
- International table and column names where DBMS is not configured with UTF-8 encoding (Teradata from version 16.00 to version 17.00).
- Treat DBMS table names and columns as case sensitive if configured (location property Case_Sensitive_Names) (Teradata from version 16.00 to version 17.00).
- Treat DBMS schema names as case sensitive if configured (location property Case_Sensitive_Names) (Teradata from version 16.00 to version 17.00).
HVR does not support the following capabilities on Teradata:
- Lossless binary float datatypes. No data loss when transporting float values (because base 2 fractions are never converted to base 10). The values for these datatypes, when selected back from the database, might be slightly different from the ones that were inserted. This leads to Compare differences..