SQLSplit
Support Me

MySQL Error 1064: SQL Syntax Error on Import

The parser rejects a statement — usually a bad split, a version mismatch, or a truncated file rather than a real syntax problem.

Common causes

  • • File split mid-statement by a non-SQL-aware tool
  • • MySQL 8 syntax imported into MariaDB or MySQL 5.7
  • • Truncated or partially downloaded dump

Best fixes

  • • Split at statement boundaries so chunks stay valid
  • • Match the export and import server versions
  • • Check the dump ends with a clean 'Dump completed' marker

Quick fix

Split the dump into smaller parts to reduce statement size and import time.

Open SQLSplit

Related guides

Errors·5 min read

MySQL Error 1064 on Import: 'You Have an Error in Your SQL Syntax'

Error 1064 during an import almost never means your dump is broken. It usually means a version mismatch or a truncated file. Here's how to pin it down.

Errors·4 min read

Fix 'Unknown collation utf8mb4_0900_ai_ci' When Importing

A MySQL 8 dump won't import into MariaDB or MySQL 5.7 because of the utf8mb4_0900_ai_ci collation. Here's the find-and-replace that fixes it.

Troubleshooting·5 min read

How to Repair a Corrupted SQL Dump

Corrupted dumps cause import errors and random failures. Here’s how to recover what you can.