Can I convert MySQL AUTO_INCREMENT to PostgreSQL?

Yes. When converting from MySQL to PostgreSQL, `INT AUTO_INCREMENT PRIMARY KEY` is transpiled to `SERIAL PRIMARY KEY` (or `BIGSERIAL` for BIGINT), and table-level engine declarations like `ENGINE=InnoDB` are removed.

Does this tool transpile LIMIT and OFFSET queries to SQL Server?

Yes. MySQL/Postgres queries using `LIMIT n` are mapped to T-SQL `TOP (n)` or standard `OFFSET n ROWS FETCH NEXT n ROWS ONLY` syntax based on your selection.

Is my proprietary SQL database schema kept private?

Yes. The transpilation engine runs 100% locally in your web browser. No table definitions or queries are sent to external servers.

SQL Dialect Converter — MySQL, PostgreSQL, SQLite & SQL Server

Why SQL Dialects Differ & How to Migrate Cleanly

Although SQL is formalized under ANSI standards, every major database management system (DBMS) has diverged significantly in its DDL syntax, identifier quoting, auto-increment mechanisms, and built-in functions. Migrating a database from MySQL to PostgreSQL, SQLite, or SQL Server often involves tedious manual editing of scripts.

Common Dialect Transformations

Identifier Escaping: MySQL uses backticks (`table`), PostgreSQL uses double quotes ("table"), and SQL Server uses brackets ([table]).
Auto-Increment Primary Keys: MySQL relies on INT AUTO_INCREMENT PRIMARY KEY, PostgreSQL uses SERIAL PRIMARY KEY, SQLite uses INTEGER PRIMARY KEY AUTOINCREMENT, and T-SQL uses INT IDENTITY(1,1) PRIMARY KEY.
String Concatenation: MySQL historically uses CONCAT(a, b), whereas PostgreSQL and SQLite use standard pipes a || b, and SQL Server uses the plus sign a + b.
Boolean Types: MySQL aliases booleans to TINYINT(1), while PostgreSQL features a native BOOLEAN type, and SQL Server uses BIT.

Frequently Asked Questions

Can this tool convert entire database dumps?

Yes. You can paste multiple CREATE TABLE statements, INSERT statements, and ALTER TABLE definitions. The transpiler processes the statements sequentially.

Does the converter handle stored procedures and triggers?

Stored procedures and procedural languages (PL/pgSQL vs T-SQL vs MySQL SP) require complex control-flow restructuring. This tool focuses on DDL schemas, constraints, indexes, data types, and standard DML queries.