Skip to main content

Capabilities for MySQL

Justin Stevenson
Updated

Capabilities for MySQL

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

Capture

HVR supports the following capabilities on MySQL:

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

HVR does not support the following capabilities on MySQL:

  • Capture from Archive log files only.
  • Log-based capture from hidden rowid/RRN column ( /CaptureFromRowId).
  • Rewind log-based capture to the beginning of currently active oldest transaction.
  • Populates column hvr_cap_user for use in {hvr_cap_user} substitutions.
  • Log-based capture checkpointing (action /CheckpointingFrequency).
  • to preserve journal/archives.
  • Read archives from an alternative directory ( /ArchiveLogPath).
  • Trigger-based capture (action /TriggerBased).

Hub Database

HVR supports Hub database on MySQL.

Integrate

HVR supports the following capabilities on MySQL:

  • changes into location (MySQL from version 5.6 to version 8.0).
  • with /Burst (MySQL from version 5.6 to version 8.0).
  • with /BurstCommitFrequency (MySQL from version 5.6 to version 8.0).
  • Continuous integration ( without /Burst) (MySQL from version 5.6 to version 8.0).
  • Action with /DuplicateRows for continuous integration (MySQL from version 5.6 to version 8.0).
  • Continuous with /OnErrorSaveFailed (without /Burst) (MySQL from version 5.6 to version 8.0).
  • Action /SoftDelete (MySQL from version 5.6 to version 8.0).
  • Bulk load requires a staging area ( /StagingDirectoryHvr) (MySQL from version 5.6 to version 8.0).
  • Creation and update of HVR state tables (MySQL from version 5.5 to version 8.0).

HVR does not support the following capabilities on MySQL:

  • Disable/enable database triggers during (/NoTriggerFiring).
  • 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 from version 5.6 to version 8.0, since HVR 5.3.1/13).
  • with /TimestampColumn (MySQL from version 5.6 to version 8.0, since HVR 5.3.1/13).

HVR does not support the following capabilities on MySQL:

  • with Log-based Capture (without /TimestampColumn).

Refresh and Compare

HVR supports the following capabilities on MySQL:

  • or from source location (MySQL from version 5.5 to version 8.0).
  • into target location (MySQL from version 5.5 to version 8.0).
  • Row-wise into target location (option -g) (MySQL from version 5.5 to version 8.0).

Other Capabilities

HVR supports the following capabilities on MySQL:

  • Call database procedure dbproc during replication jobs (action /DbProc) (MySQL from version 5.6 to version 8.0).
  • International table and column names where DBMS is not configured with UTF-8 encoding (MySQL from version 5.5 to version 8.0).
  • Treat DBMS table names and columns as case sensitive if configured (action /CaseSensitiveNames defined) (MySQL from version 5.5 to version 8.0).
  • Always treat DBMS table names and column names as case sensitive, even if not configured (action /CaseSensitiveNames not defined) (MySQL from version 5.5 to version 8.0).
  • Always treat DBMS schema names case sensitive (MySQL from version 5.5 to version 8.0).

HVR does not support the following capabilities on MySQL:

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

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk