Capabilities for MySQL

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

Capture

HVR supports the following capabilities on MySQL:

• Capture changes from location (MySQL from version 5.6 to version 8.0).
• 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 of tables with LOB column (MySQL from version 5.6 to version 8.0).
• Rewind log-based capture to specific time (hvractivate option -i) (MySQL from version 5.6 to version 8.0).
• 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).
• 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 (ColumnProperties with parameter CaptureFromRowId).
• Rewind log-based capture to the beginning of currently active oldest transaction.
• Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
• Log-based capture checkpointing using location property Capture_Checkpoint_Frequency.
• Read archives from an alternative directory (location property Archive_Log_Path on the capture location).
• Trigger-based capture (location property Capture_Method=DB_TRIGGER on the capture location).

Repository Database

HVR supports Repository database on MySQL.

Integrate

HVR supports the following capabilities on MySQL:

• Integrate changes into location (MySQL from version 5.6 to version 8.0).
• Burst integration (Integrate with parameter Method=BURST) (MySQL from version 5.6 to version 8.0).
• Integrate with parameter BurstCommitFrequency (MySQL from version 5.6 to version 8.0).
• Continuous integration (Integrate with parameter Method=CONTINUOUS) (MySQL from version 5.6 to version 8.0).
• Tables without a key and without TableProperties with NoDuplicateRows for continuous integration (MySQL from version 5.6 to version 8.0).
• Continuous integrate with parameter OnErrorSaveFailed (MySQL from version 5.6 to version 8.0).
• ColumnProperties with parameter SoftDelete (MySQL from version 5.6 to version 8.0).
• Bulk load requires a staging area (location property Staging_Directory) (MySQL from version 5.6 to version 8.0).
• Creation and update of HVR state tables (MySQL from version 5.6 to version 8.0).

HVR does not support the following capabilities on MySQL:

• Disable/enable database triggers during integrate (with parameter NoTriggerFiring).
• Integrate with parameter 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).
• CollisionDetect with parameter TimestampColumn (MySQL from version 5.6 to version 8.0).

HVR does not support the following capabilities on MySQL:

• CollisionDetect with Log-based Capture (without parameter TimestampColumn).

Refresh and Compare

HVR supports the following capabilities on MySQL:

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

Other Capabilities

HVR supports the following capabilities on MySQL:

• Call database procedure dbproc during replication jobs (AgentPlugin with parameter 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.6 to version 8.0).
• Always treat DBMS table names and column names as case sensitive, even if not configured (equivalent to location property Case_Sensitive_Names always set to TRUE) (MySQL from version 5.6 to version 8.0).
• Always treat DBMS schema names case sensitive (MySQL from version 5.6 to version 8.0).

HVR does not support the following capabilities on MySQL:

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