MySQL specifics
We can't guarantee data migration scenarios between major versions with a minor version.
- Make sure that full binary log mode is enabled for the source database.
- Working with constraints (
CONSTRAINT
).- Constraints (
CONSTRAINT
) are enabled on the target by default. This is taken into account during the transfer. For large databases, this can significantly affect replication performance. - At the transfer level, you can disable
CONSTRAINT
to regain performance. However, the behavior may vary depending on the low-level data storage subsystem: unlike MyISAM, we can't guarantee cascade delete for InnoDB.
- Constraints (
- Only the MyISAM and InnoDB low-level storage subsystems are tested regularly. We don't guarantee that the other low-level storage subsystems will behave properly.
- Running the
ALTER
operators:- In some cases, such operators may slow down replication, but the performance usually recovers after a while.
- If you perform complex manipulations that involve changing the schema on the source, run explicit checks on the target database.
- You can change the limit on the size of the chunk sent using the
max_allowed_packet
parameter. - SQL mode must be the same on the source and target.
The transfer checks this requirement and, if any discrepancy is found, requests administrator intervention.