Homogeneous replication
The following section describes how Replicate handles replication between a MySQL source and the following targets: MySQL, Microsoft Azure Database for MySQL, and Google Cloud SQL for MySQL.
-
In homogeneous replication, the source data first passes through the Qlik Replicate data type and is therefore subject to any limitations of that type.
For information on Replicate data types and their limitations (where relevant), see Replicate data types.
For information on which Replicate data types the source data passes through when replicating from MySQL, see the MySQL to Qlik Replicate data types mapping table described earlier.
- When replicating a TIMESTAMP column, the time is converted to UTC on the target.
Limitations and considerations
Homogeneous replication is not supported with the following Replicate configurations or operations:
- Apply Changes only tasks
- Stopping and resuming a task
- Starting a task from a timestamp
- When the If target table already exists in the task settings' Full Load Settings tab is set to Do nothing
Data types
The data types will be identical with the following exceptions:
| MySQL Source Data Types | MySQL-based Target Data Types |
|---|---|
| JSON | LONGTEXT |
When using data types from other database engines, the data type on the target will be the corresponding MySQL data type. For more information on using non-native data types, refer to the MySQL online Help.
Collation
Table and column collations will be replicated to the target. Collatable data types are indicated by an asterisk (*) in the Supported data types table.
To support collation replication, the DBA must ensure that the collations defined for the source MySQL database are the same as those defined for the MySQL-based target database.
Non-nullable columns and primary/unique index names
Non-nullable columns and Primary/Unique Index names are preserved during homogeneous replication.