SQL is a text language: a statement is a string you can read, format and check before it ever reaches a database. Treating it as text first is what makes review and migration safer.
01A safe order of operations
Validate the statement structurally for the right dialect so an unbalanced quote or parenthesis surfaces early.
Check for destructive statements — DROP, TRUNCATE or a DELETE without WHERE — before anything runs.
Format or minify the text, and split a script into statements to review them one at a time.
02Dialects change the rules
MySQL accepts backtick identifiers and backslash escapes; T-SQL uses square brackets; PostgreSQL adds dollar-quoted strings. Choosing the dialect keeps every check honest, and none of these tools opens a connection or runs a statement.
Frequently asked questions
Do these tools run my SQL?
No. Every statement is processed as text in your browser; no database connection is opened and nothing is executed.
Which dialects are supported?
PostgreSQL, MySQL, SQLite and T-SQL, plus a generic standard mode for dialect-neutral SQL.
Check a SQL statement for structural problems such as unbalanced parentheses, unterminated strings or comments, and an unrecognised leading command, for PostgreSQL, MySQL, SQLite or T-SQL, locally in your browser.
A practical guide to choosing random passwords and tokens, deriving and storing password hashes, signing tokens, encrypting with authenticated modes and measuring entropy.