Is converting mysqldump to Microsoft SQL Server 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 mysqldump data keep its types in Microsoft SQL Server?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real Microsoft SQL Server 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.

Convert mysqldump to Microsoft SQL Server

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

1Upload your file

Click to upload or drag and drop

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

2Choose target format

How your data is typed in Microsoft SQL Server

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

Your data	Microsoft SQL Server type
Whole number	BIGINT
Decimal (money)	DECIMAL(10,2)
Floating point	FLOAT
True / false	BIT
Date	DATE
Date and time	DATETIME2
Short text	NVARCHAR(255)
Long text	NVARCHAR(MAX)
Binary data	VARBINARY(MAX)

Working from a mysqldump file

mysqldump writes a plain-text .sql file with a very consistent shape, which makes it one of the easiest dumps to read: its own syntax announces the dialect, and its rows are inline rather than in a separate archive.

→Every mysqldump file contains ENGINE=InnoDB or AUTO_INCREMENT, which is exactly what the dialect detection looks for, so backtick-quoted identifiers and MySQL types parse without you choosing anything.
→mysqldump packs many rows into one extended INSERT by default, and each tuple in it becomes a row, so there is no need to dump again with --skip-extended-insert.
→The file is decoded as UTF-8 with unreadable bytes replaced, so a legacy latin1 dump arrives with damaged accented text. Dump with --default-character-set=utf8mb4, or run the file through iconv first.
→mysqldump --tab is not a dump at all: the schema goes to a .sql file and the rows to headerless tab-separated .txt files. Neither half is convertible on its own, and the data files have no header row to name their columns, so dump again without --tab.

Which SQL Server this runs on

Microsoft SQL Server is the full product name, and it covers a wide range of places to put a database: Express on a laptop, a Developer instance, a Linux container, a managed Azure SQL database. The script was written not to care which of them it lands in.

→There is no CREATE DATABASE, no USE, and no filegroup or collation clause anywhere in the file, so nothing in it can be refused by an edition that forbids those. Which database it populates is decided by your client's connection.
→No schema is named either, so the tables land in the default schema of whichever login runs the script - dbo for most logins. Moving them elsewhere afterwards is an ALTER SCHEMA ... TRANSFER.
→The primary key is emitted as an unnamed constraint, which the server materialises as a clustered index under a name it invents. Nothing else is indexed, so any index the source carried has to be rebuilt by hand.

Reading mysqldump

→Parsed with a real SQL parser, not regular expressions, so a value containing a closing parenthesis or a semicolon cannot split a row in half.
→CREATE TABLE types, primary keys, NOT NULL and AUTO_INCREMENT are all read from the dump.
→The source dialect is detected from the dump itself — MySQL, PostgreSQL and SQL Server dumps all parse.

Writing Microsoft SQL Server

→String literals carry the N prefix, so non-ASCII text survives whatever collation the database uses.
→Timestamps become DATETIME2. T-SQL’s TIMESTAMP is a row-version counter, not a point in time.
→Identity columns are wrapped in SET IDENTITY_INSERT so explicit key values load.
→Statements are separated with GO in batches.

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 SQL Server:

  sqlcmd -S HOST -U USER -P PASSWORD -d DATABASE -i dump.sql

Notes:

  - Text columns are NVARCHAR and literals carry the N prefix, so
    non-ASCII data survives regardless of database collation.
  - Timestamps are DATETIME2. T-SQL's TIMESTAMP type is a row
    version, not a point in time.

Questions

Is converting mysqldump to Microsoft SQL Server 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 mysqldump data keep its types in Microsoft SQL Server?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real Microsoft SQL Server 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.