A few terms come up regularly in SQLmig. Knowing them is enough to understand most screens.
| Term | Simple definition |
|---|---|
| Database | A logical collection of tables and objects managed by MySQL or MariaDB. |
| Source | The server from which databases are read for backup or migration. |
| Cible | The server that receives databases during an import or migration. |
| Dump | An SQL file representing the structure and data of one or more databases. |
| Separate dump | A mode in which each database has its own SQL file. |
| Combined dump | A mode in which multiple databases are combined into a single SQL file. |
| Import / restore | Lecture d’un dump SQL et création des objets/données sur un serveur Target. |
| Logical migration | Transferring databases using an SQL dump, as opposed to a physical copy of the database engine files. |
| Pre-check | An analysis performed before a migration to identify incompatibilities or risks. |
| Collation | The rules used to compare and sort text in a database. |
| DEFINER | The account associated with certain SQL objects such as views, routines, or events. |
| TLS / SSL | An encryption mechanism for a network connection between SQLmig and an SQL server. |
| max_allowed_packet | A MySQL/MariaDB limit that can affect the import of very large INSERT statements or BLOBs. |
| Restricted mode | Mode without a valid license: backup is available on only one server, while migration/import are disabled. |
Need a quick reference?
For a backup: Source → databases → dump. For a migration: Source + Target → databases → pre-checks → dump → import. For a restore: dump → Target → databases → import.