Convert DDB to MariaDB

Upload a .duckdb or .ddb file and get back a MariaDB SQL script you can load straight into your database. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.

Click to upload or drag and drop

CSV, Excel, SQLite, SQL, DBF (max 10 MB)

How your data is typed in MariaDB

Generated from the converter's own MariaDB type mapping — this is what it actually emits, not an example.

Your dataMariaDB type
Whole numberBIGINT
Decimal (money)DECIMAL(10,2)
Floating pointDOUBLE
True / falseTINYINT(1)
DateDATE
Date and timeDATETIME
Short textVARCHAR(255)
Long textLONGTEXT
Binary dataLONGBLOB

Working from a .ddb file

.ddb is the short form of the DuckDB extension, and DuckDB itself does not care what you call a database file. The uploader does: it routes on the extension alone, so the name you saved under decides which reader ever sees the file.

  • .ddb and .duckdb both reach the DuckDB reader and are read identically. Nothing inside the file records which of the two you chose - the storage version is in the header, the name is not.
  • One file is this format's whole promise, so make sure it really is one file before you send it: closing the DuckDB CLI cleanly, or running CHECKPOINT first, folds the write-ahead log back into the database itself.
  • A file with no extension at all, which DuckDB is perfectly happy to create, is not recognised as anything and is refused before it is read.

What MariaDB gets, and how it differs

MariaDB and MySQL are close enough here that one dialect serves both, and picking MariaDB does not select a different code path: the script is byte for byte the one a MySQL conversion produces. The differences worth flagging are in what you do with it.

  • The README packed beside the script names both engines in its load command, because the invocation is the same either way - the file is piped into a client rather than executed by the server.
  • The CREATE DATABASE line in that README asks for utf8mb4_unicode_ci and not for utf8mb4_0900_ai_ci, which is MySQL 8's default. MariaDB has never implemented the 0900 collations, and unicode_ci is the one both engines have.
  • Date-and-time columns are declared DATETIME rather than TIMESTAMP, so what loads is the wall-clock value the source held. No session time zone is applied on the way in, and none is applied when you read it back out.

Reading DDB

  • Types, primary keys and NOT NULL constraints are read from the database.
  • The file is opened read-only, so your upload is never modified or upgraded in place.

Writing MariaDB

  • Tables are created as InnoDB with utf8mb4, so emoji and CJK text survive the load.
  • Backslashes are escaped, because MySQL treats them as escape characters by default.
  • Text columns of unknown length become TEXT rather than a guessed VARCHAR that could truncate your data.
  • Inserts are batched, and identifiers are capped at MySQL’s 64-character limit.

What you get

A ZIP containing dump.sql, plus a README with the exact command to load it. If anything about your data needed a judgement call, a _warnings.txt explains it.

Load this dump into MySQL or MariaDB:

  mysql -u USER -p DATABASE < dump.sql

Create the database first if it does not exist:

  mysql -u USER -p -e "CREATE DATABASE DATABASE CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"

Questions

Is converting DDB to MariaDB free?
Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
Will my DDB data keep its types in MariaDB?
Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real MariaDB types rather than everything becoming text. The mapping table above shows exactly what you get.
Do you store my file?
No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.

This conversion, under other names

Convert DDB to something else

Convert something else to MariaDB