Capabilities for Redshift

Last updated on Jul 23, 2020

Contents

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

Capture

HVR does not support Capture changes from location on Redshift.

Hub Database

HVR does not support Hub database on Redshift.

Integrate

HVR supports the following capabilities on Redshift:

  • Integrate changes into location (Redshift version 1.0).
  • Integrate with /Burst (Redshift version 1.0).
  • Integrate with /BurstCommitFrequency (Redshift version 1.0).
  • Continuous integration (Integrate without /Burst) (Redshift version 1.0).
  • Action Transform /SoftDelete (Redshift version 1.0).
  • Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (Redshift version 1.0).
  • Creation and update of HVR state tables (Redshift version 1.0).

HVR does not support the following capabilities on Redshift:

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

Other Capabilities

HVR supports the following capabilities on Redshift:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /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 case sensitive (action LocationProperties /CaseSensitiveNames) (Redshift version 1.0, since HVR 5.6.5/1).

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