Capabilities for Vector

From HVR
Jump to: navigation, search

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

Capture

HVR does not support Capture changes from location on Vector


HVR Hub

HVR supports Hub database (Vector version 2.0 and above)


Integrate

HVR supports the following capabilities on Vector:

  • Integrate changes into location (Vector version 2.0 and above)
  • Integrate with /Burst (Vector version 2.0 and above)
  • Integrate with /BurstCommitFrequency (Vector version 2.0 and above)
  • Continuous integration (Integrate without /Burst) (Vector version 2.0 and above)
  • Action TableProperties with /DuplicateRows for continuous integration (Vector version 2.0 and above)
  • Action Transform /SoftDelete (Vector version 2.0 and above)
  • Creation and update of HVR state tables


HVR does not support the following capabilities on Vector:

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


Refresh and Compare

HVR supports the following capabilities on Vector:

  • Refresh or Compare from source location
  • Refresh into target location
  • Row-wise refresh into target location (option -g)
  • Disable/enable foreign keys and secondary indices during refresh (option -F)
  • For a table: disable/enable journaling, disable/enable unique/primary constraints, disable/enable volatile secondary indices, support main storage structure during refresh


HVR does not support the following capabilities on Vector:


Other Capabilities

HVR supports the following capabilities on Vector:

  • International table and column names where DBMS is not configured with UTF-8 encoding


HVR does not support the following capabilities on Vector:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey)
  • Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10)