SQL Splitter: Split and compress an SQL file

Either one .sql.gz that phpMyAdmin can import directly, or multiple .sql files, each under your limit. The parts are available individually and as a ZIP, optionally also as .sql.gz and as text to copy. community-db.sql (98 KB) becomes 20 KB as .sql.gz, or 3 parts when split at a target size of 40 KB. Each part includes the dump header and is listed in import order. The tool also shows each part's size, statements and tables.

phpMyAdmin receives files through PHP, which limits upload size (upload_max_filesize and post_max_size). On our database servers, the limit is 2 MB; phpMyAdmin displays this under Import as “Maximum size: 2,048 KiB”. Text you paste into the SQL tab is subject to the same limit. That's why the tool has a “Paste into SQL console” mode: it calculates the size the browser actually sends and makes the chunks smaller accordingly.

Often, yes. The limit applies to the uploaded file—the compressed one—and SQL dumps contain a lot of repeated text. phpMyAdmin decompresses a .sql.gz file itself during import. The SQL Splitter calculates the .sql.gz size first, shows you how much smaller it is, and recommends splitting only if the compressed file still exceeds your limit.

Load a .sql, .sql.gz or .zip file into the SQL Splitter, such as an export from mysqldump, mariadb-dump, phpMyAdmin, HeidiSQL or Adminer. It splits only between complete statements: the tool recognizes strings with escapes, comments, /*!…*/ lines and DELIMITER blocks for triggers and procedures, so semicolons inside them do not cause a split. If a multi-row INSERT is larger than one part, it is divided between records into multiple INSERTs with the same statement header. If a single record exceeds the target size, usually an image in a BLOB column, the tool identifies the statement number, line and table. Import that part with HeidiSQL or the mysql client, or try uploading it as .sql.gz.

Import the numbered parts in order, starting with part 1, all into the same database. Part 1 usually contains the CREATE TABLE statements; later parts populate the tables. If the dump has foreign keys, each part disables foreign key checks at the start and re-enables them at the end. If a part fails, fix the error and resume with that same part. Do not import earlier parts again, or you'll get “Table already exists” or “Duplicate entry”. If you're unsure what's already been imported, empty the database (in phpMyAdmin, select and drop all tables on the Structure tab) and start again with part 1.

Views, triggers, procedures, and events store the user account they run under (DEFINER). If that account belongs to the old server, such as root, your database user cannot create them. Select “Remove DEFINER” in the tool, and the server will create them under your user account. MariaDB calls the missing privilege SET USER. If the dump comes from MySQL, the SQL_LOG_BIN (BINLOG ADMIN privilege) and GTID_PURGED lines may also fail; use “Remove replication lines” for those.

utf8mb4_0900_ai_ci is the default collation in MySQL 8. MariaDB doesn't support it, even in version 11.6, and stops at CREATE TABLE with error #1273. The “Replace MySQL 8 collations” fix replaces it and the other 0900 variants with utf8mb4_unicode_ci, and the case-sensitive variants with utf8mb4_bin. It leaves INSERT statements—and therefore your data—unchanged.

No. Dumps often contain customer data and credentials, so the tool reads the file only in your browser, in a Web Worker. There is no upload, storage, or account. In the developer tools’ Network tab, you can see that compressing and splitting sends no request containing your file.