Capabilities for Aurora MySQL

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

Capture

HVR supports the following capabilities on Aurora MySQL:

• Capture changes from location (Aurora MySQL from 1.0 to 3.0).
• Log-based capture (capture from DBMS logging system) (Aurora MySQL from 1.0 to 3.0).
• Log-based capture of DDL statements using action AdaptDDL (Aurora MySQL from 1.0 to 3.0).
• Log-based capture of tables without a primary key (Aurora MySQL from 1.0 to 3.0).
• Access to logs using SQL interface (Aurora MySQL from 1.0 to 3.0).
• Log-based capture of tables with LOB column (Aurora MySQL from 1.0 to 3.0).
• Rewind log-based capture to specific time (hvractivate option -i) (Aurora MySQL from 1.0 to 3.0).
• Online refresh using accurate LSN/SCN (Aurora MySQL from 1.0 to 3.0).
• Log-based capture of truncate table statements (Aurora MySQL from 1.0 to 3.0).
• Multiple log-based capture jobs can capture from same database (Aurora MySQL from 1.0 to 3.0).
• Capture from tables with any compression (Aurora MySQL from 1.0 to 3.0).

HVR does not support the following capabilities on Aurora MySQL:

• Capture from Archive log files only.
• Log-based capture of DDL statements (AdaptDDL) without refresh.
• Direct access to logs on a file system.
• 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 (using the location property Capture_Method=DB_TRIGGER at the capture location). This method has been deprecated since 6.2.0/0..

Repository Database

HVR supports Repository database on Aurora MySQL.

Integrate

HVR supports the following capabilities on Aurora MySQL:

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

HVR does not support the following capabilities on Aurora MySQL:

• Append integration into TimeKey (Integrate with parameter Method=APPEND).
• Disable/enable database triggers during integrate (with parameter NoTriggerFiring).
• Integrate with parameter DbProc.

Bi-directional Replication

HVR supports the following capabilities on Aurora MySQL:

• Detection of changes made by HVR in a bidirectional channel to prevent loop-back (Aurora MySQL from 1.0 to 3.0).
• CollisionDetect with parameter TimestampColumn (Aurora MySQL from 1.0 to 3.0).

HVR does not support the following capabilities on Aurora MySQL:

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

Refresh and Compare

HVR supports the following capabilities on Aurora MySQL:

• hvrrefresh or hvrcompare from source location (Aurora MySQL from 1.0 to 3.0).
• hvrrefresh into target location (Aurora MySQL from 1.0 to 3.0).
• Isolated table hvrrefresh (option -i) into target location (Aurora MySQL from 1.0 to 3.0).
• Row-wise hvrrefresh into target location (option -g) (Aurora MySQL from 1.0 to 3.0).

Other Capabilities

HVR supports the following capabilities on Aurora MySQL:

• Call database procedure dbproc during replication jobs (AgentPlugin with parameter DbProc) (Aurora MySQL from 1.0 to 3.0).
• International table and column names where DBMS is not configured with UTF-8 encoding (Aurora MySQL from 1.0 to 3.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) (Aurora MySQL from 1.0 to 3.0).
• Always treat DBMS schema names case sensitive (Aurora MySQL from 1.0 to 3.0).

HVR does not support the following capabilities on Aurora MySQL:

• Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey).