Capabilities for MariaDB
This section lists the Capabilities of HVR when using 'MariaDB'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for MySQL and MariaDB.
Capture
HVR supports the following capabilities on MariaDB:
- Capture changes from location (MariaDB from version 10.0 to version 10.3, since HVR 5.3.1/13).
- Log-based capture (capture from DBMS logging system) (MariaDB from version 10.0 to version 10.3).
- Log-based capture of tables without a primary key (MariaDB from version 10.0 to version 10.3).
- Direct access to logs on a file system (MariaDB from version 10.0 to version 10.3, except on Amazon RDS for MariaDB, and Microsoft Azure Database for MariaDB).
- Access to logs using SQL interface (MariaDB from version 10.0 to version 10.3).
- Log-based capture with /LogReadMethod parameter (MariaDB from version 10.0 to version 10.3).
- Log-based capture of tables with LOB column (MariaDB from version 10.0 to version 10.3).
- Rewind log-based capture to specific time (Hvrinit option -i) (MariaDB from version 10.0 to version 10.3, since HVR 5.3.1/15).
- Online refresh using accurate LSN/SCN (MariaDB from version 10.0 to version 10.3).
- Log-based capture of truncate table statements (MariaDB from version 10.0 to version 10.3, since HVR 5.3.1/21).
- Multiple log-based capture jobs can capture from same database (MariaDB from version 10.0 to version 10.3).
- Capture from tables with any compression (MariaDB from version 10.0 to version 10.3).
HVR does not support the following capabilities on MariaDB:
- Capture from Archive log files only.
- Log-based capture from hidden rowid/RRN column (ColumnProperties /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 (action Capture /CheckpointingFrequency).
- Hvrlogrelease to preserve journal/archives.
- Read archives from an alternative directory (Capture /ArchiveLogPath).
- Trigger-based capture (action Capture /TriggerBased).
Hub Database
HVR supports Hub database on MariaDB.
Integrate
HVR supports the following capabilities on MariaDB:
- Integrate changes into location (MariaDB from version 10.0 to version 10.3).
- Integrate with /Burst (MariaDB from version 10.0 to version 10.3).
- Integrate with /BurstCommitFrequency (MariaDB from version 10.0 to version 10.3).
- Continuous integration (Integrate without /Burst) (MariaDB from version 10.0 to version 10.3).
- Action TableProperties with /DuplicateRows for continuous integration (MariaDB from version 10.0 to version 10.3).
- Continuous Integrate with /OnErrorSaveFailed (without /Burst) (MariaDB from version 10.0 to version 10.3).
- Action Transform /SoftDelete (MariaDB from version 10.0 to version 10.3).
- Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (MariaDB from version 10.0 to version 10.3).
- Creation and update of HVR state tables (MariaDB from version 5.5 to version 10.3).
HVR does not support the following capabilities on MariaDB:
Bi-directional Replication
HVR supports the following capabilities on MariaDB:
- Detection of changes made by HVR in a bidirectional channel to prevent loop-back (MariaDB from version 10.0 to version 10.3, since HVR 5.3.1/13).
- CollisionDetect with /TimestampColumn (MariaDB from version 10.0 to version 10.3, since HVR 5.3.1/13).
HVR does not support the following capabilities on MariaDB:
- CollisionDetect with Log-based Capture (without /TimestampColumn).
Refresh and Compare
HVR supports the following capabilities on MariaDB:
- Hvrrefresh or Hvrcompare from source location (MariaDB from version 5.5 to version 10.3).
- Hvrrefresh into target location (MariaDB from version 5.5 to version 10.3).
- Row-wise Hvrrefresh into target location (option -g) (MariaDB from version 5.5 to version 10.3).
Other Capabilities
HVR supports the following capabilities on MariaDB:
- Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (MariaDB from version 10.0 to version 10.3).
- International table and column names where DBMS is not configured with UTF-8 encoding (MariaDB from version 5.5 to version 10.3).
- Treat DBMS table names and columns as case sensitive if configured (action LocationProperties /CaseSensitiveNames defined) (MariaDB from version 5.5 to version 10.3).
- Always treat DBMS table names and column names as case sensitive, even if not configured (action LocationProperties /CaseSensitiveNames not defined) (MariaDB from version 5.5 to version 10.3).
- Always treat DBMS schema names case sensitive (MariaDB from version 5.5 to version 10.3).
HVR does not support the following capabilities on MariaDB:
- 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).