SQLParity

SQL Converter

Rewrite quoting, escaping, row limits and function names between 16 dialects, with a list of what it refused to guess at.

1

SQL Server (T-SQL) query

2

PostgreSQL query

3

Check it on a real engine

Runs the converted query on a real PostgreSQL engine inside this tab.

Sample tables

Guessed from the query

Created in memory for each run and thrown away afterwards. Paste your real CREATE TABLE and a few rows for an exact check.

What the check does
  1. 1Starts a real PostgreSQL in this tab, downloaded from this site the first time only.
  2. 2Creates the sample tables on the left, in memory.
  3. 3Runs the converted query and shows what it returns, or the exact error.
  4. 4Throws the tables away. Nothing is sent anywhere.

What it changed

  • TOP 10LIMIT 101 place
  • [name]"name"8 places
  • ISNULL()COALESCE()1 place
  • LEN(x)LENGTH(RTRIM(x))1 place
  • current timestampCURRENT_TIMESTAMP1 place

What you still need to do

Nothing in this query is the kind of thing that translates wrongly. Still run it once before you trust it.

Anything left in this list was recognised and left as it was on purpose. A function renamed to one that takes its arguments in a different order produces SQL that runs and returns the wrong rows, which is worse than SQL that fails.

How to Use SQL Dialect Converter

How to translate SQL queries between 16 database engines without data leaks.

1

Choose From & To Dialects

Select your source database engine in the "From" dropdown and your destination database in the "To" dropdown.

2

Paste Your Query

Paste your original SQL query into the left panel. The tool begins converting immediately as you type.

3

Inspect Receipts & Copy

Review the rewritten query, check the list of changes made, and review any items flagged for human verification.

Frequently Asked Questions

Common questions about privacy, supported dialects, and how SQL Dialect Converter works under the hood.

What syntax differences does SQLParity translate automatically?

It translates identifier delimiters (brackets to quotes or backticks), row limit syntax (TOP n vs. LIMIT n), string escaping rules, date functions, null checks (ISNULL to COALESCE), and string length functions (LEN to LENGTH with RTRIM).

What does "What you still need to do" mean in the SQL Converter?

Instead of blindly guessing at complex stored procedures or proprietary engine functions and returning SQL that fails silently, SQLParity lists any non-portable constructs that require manual human review.

Can I check that the converted query actually runs?

Yes, when the target is PostgreSQL, SQLite or DuckDB. The converted query runs on that real database engine inside your browser tab, against sample tables guessed from the query that you can edit. When the source is one of the three as well, the original runs alongside it on the same data and the two results are compared row by row.

Are queries sent to an AI backend or third-party translation server?

No. The entire conversion logic runs locally inside your browser tab using deterministically tested parsers and tokenizers. No queries are uploaded or logged.

How many database pairs can I convert between?

All 16 supported dialects can be converted to any other dialect, providing 240 pairwise translation paths including SQL Server to Postgres, MySQL to Snowflake, and Oracle to BigQuery.

Browse SQL conversions by source database

Choose the database your query uses now, then the database you want to convert it to.

Convert from PostgreSQL
Convert from MySQL
Convert from SQLite
Convert from SQL Server (T-SQL)
Convert from Oracle
Convert from MariaDB
Convert from Snowflake
Convert from Google BigQuery
Convert from Amazon Redshift
Convert from Amazon Athena / Trino
Convert from Apache Spark SQL
Convert from Apache Hive
Convert from ClickHouse
Convert from DuckDB
Convert from IBM Db2
Convert from Standard SQL