Capabilities for MySQL

From HVR
Jump to: navigation, search

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

Capture

HVR supports the following capabilities on MySQL:

  • Capture changes from location (MySQL version 5.6 and above, since HVR 5.3.1/13)
  • Log-based capture (capture from DBMS logging system) (MySQL version 5.6 and above)
  • Log-based capture of tables without a primary key (MySQL version 5.6 and above)
  • Direct access to logs on a file system (MySQL version 5.6 and above)
  • Access to logs using SQL interface (MySQL version 5.6 and above)
  • Log-based capture with /LogReadMethod param (MySQL version 5.6 and above)
  • Log-based capture of tables with LOB column (MySQL version 5.6 and above)
  • Rewind log-based capture to specific time (hvrinit option -i) (MySQL version 5.6 and above, since HVR 5.3.1/15)
  • Online refresh using accurate LSN/SCN (MySQL version 5.6 and above)
  • Log-based capture of truncate table statements (MySQL version 5.6 and above, since HVR 5.3.1/21)
  • Multiple log-based capture jobs can capture from same database (MySQL version 5.6 and above)
  • Capture from tables with any compression (MySQL version 5.6 and above)


HVR does not support the following capabilities on MySQL:

  • Log-based capture from hidden rowid column (ColumnProperties /CaptureFromRowId)
  • Rewind log-based capture to the beginning of currently active oldest transaction (MySQL version 5.6 and above)
  • Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions (MySQL version 5.6 and above)
  • Log-based capture checkpointing (action Capture /CheckpointingFrequency) (MySQL version 5.6 and above)
  • hvrlogrelease to preserve journal/archives
  • Read archives from an alternative directory (Capture /ArchiveLogPath)
  • Trigger-based capture (action Capture /TriggerBased) (MySQL version 5.6 and above)


HVR Hub

HVR supports Hub database (MySQL version 5.6 and above)


Integrate

HVR supports the following capabilities on MySQL:

  • Integrate changes into location (MySQL version 5.6 and above)
  • Integrate with /Burst (MySQL version 5.6 and above)
  • Integrate with /BurstCommitFrequency (MySQL version 5.6 and above)
  • Continuous integration (Integrate without /Burst) (MySQL version 5.6 and above)
  • Action TableProperties with /DuplicateRows for continuous integration (MySQL version 5.6 and above)
  • Continuous integrate with /OnErrorSaveFailed (without /Burst) (MySQL version 5.6 and above)
  • Action Transform /SoftDelete (MySQL version 5.6 and above)
  • Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (MySQL version 5.6 and above)
  • Creation and update of HVR state tables


HVR does not support the following capabilities on MySQL:

  • Disable/enable database triggers during integrate (/NoTriggerFiring)
  • Integrate with /DbProc


Bi-directional Replication

HVR supports the following capabilities on MySQL:

  • Detection of changes made by HVR in a bidirectional channel to prevent loop-back (MySQL version 5.6 and above, since HVR 5.3.1/13)
  • Collision Detect with /TimestampColumn (MySQL version 5.6 and above, since HVR 5.3.1/13)


HVR does not support the following capabilities on MySQL:


Refresh and Compare

HVR supports the following capabilities on MySQL:


Other Capabilities

HVR supports the following capabilities on MySQL:

  • Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames)


HVR does not support the following capabilities on MySQL:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey)
  • 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)