Capabilities for Redshift

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

Capture

HVR does not support Capture changes from location on Redshift.

Repository Database

HVR does not support Repository database on Redshift.

Integrate

HVR supports the following capabilities on Redshift:

• Integrate changes into location (Redshift version 1.0).
• Burst integration (Integrate with parameter Method=BURST) (Redshift version 1.0).
• Integrate with parameter BurstCommitFrequency (Redshift version 1.0).
• Continuous integration (Integrate with parameter Method=CONTINUOUS) (Redshift version 1.0).
• ColumnProperties with parameter SoftDelete (Redshift version 1.0).
• Bulk load requires a staging area (location property Staging_Directory) (Redshift version 1.0).
• Creation and update of HVR state tables (Redshift version 1.0).

HVR does not support the following capabilities on Redshift:

• 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 Redshift.

Refresh and Compare

HVR supports the following capabilities on Redshift:

• hvrrefresh or hvrcompare from source location (Redshift version 1.0).
• hvrrefresh into target location (Redshift version 1.0).
• Row-wise hvrrefresh into target location (option -g) (Redshift version 1.0).

HVR does not support the following capabilities on Redshift:

• Bulk load of multiple slices of same table can be done in parallel.

Other Capabilities

HVR supports the following capabilities on Redshift:

• Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey) (Redshift version 1.0).
• International table and column names where DBMS is not configured with UTF-8 encoding (Redshift version 1.0).
• Treat DBMS table names and columns as case sensitive if configured (location property Case_Sensitive_Names) (Redshift version 1.0).
• Treat DBMS schema names as case sensitive if configured (location property Case_Sensitive_Names) (Redshift version 1.0).

HVR does not support the following capabilities on Redshift:

• 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..