Configures the MySQL/MariaDB server type and the default charset and collation for the converted schema.
Select MySQL or MariaDB to match the target server. Affects certain SQL constructs in the generated script (collation syntax, server-specific defaults).
The server panel mirrors the key information from the Remote Configuration tab (version, max packet, server charset, table name case-sensitivity). It is read-only here and updates when Get Server Information is run.
| Option | Description |
|---|---|
| Default settings | Combo boxes populated with a standard built-in list. |
| Server settings | Combo boxes populated with charsets and collations actually available on the connected server. Recommended when a connection is available. |
Used in CREATE DATABASE and CREATE TABLE
statements as the schema-wide default. Also the fallback for any column
whose EDB collation cannot be resolved through the collation map.
These values apply at schema level only. Each text column (
CHAR,VARCHAR,CLOB) is resolved individually through the collation map and receives its ownCOLLATEclause when the result differs from the table default. The charset and collation set here are used in two situations only: as theDEFAULT CHARSET/DEFAULT COLLATEinCREATE TABLE, and as the fallback for columns whose EDB collation cannot be mapped — see How Collation Mapping Works.
| Field | Description |
|---|---|
| Default Charset | MySQL/MariaDB character set (e.g. utf8mb4). |
| Default Collation | Collation for the charset
(e.g. utf8mb4_unicode_ci). |
Recommended for this source database — after opening a source database, EDB2MySQL suggests the most appropriate charset and collation based on the collations found in the database. The suggestion is shown here; click it to apply.
The universal safe fallback is
utf8mb4/utf8mb4_bin. Guaranteed to exist on any MySQL or MariaDB server; preserves exact byte values for all text.
Click Edit Collations Map to customise how individual EDB collations are mapped.