a apiary.
← All tools

SQL / BROWSER UTILITY

SQL Syntax Checker

Check SQL syntax, common mistakes and potential performance issues locally for Oracle, SQL Server, PostgreSQL, MySQL/MariaDB and SQLite.

Checked locally in your browser. Your SQL is not uploaded or executed.

Oracle: Apiary lint only. No Oracle grammar parser is installed. This is not full Oracle SQL or PL/SQL validation.

Up to 100,000 characters. Choose a diagnostic’s location to select that SQL fragment.

Review options

Local pattern checks only, without AI. Actual cost depends on the execution plan, indexes, statistics and table sizes. No query is run.

Have an execution plan?

Execution plans can provide much stronger performance clues. Apiary analyses the plan locally and does not connect to your database.

Use the selected SQL dialect. Supported: PostgreSQL text EXPLAIN, MySQL/MariaDB traditional pipe/tab EXPLAIN tables, SQLite QUERY PLAN text, Oracle DBMS_XPLAN tables, and SQL Server SHOWPLAN_TEXT operator trees. XML/JSON plans are not supported. Up to 100,000 characters, 2,000 lines and 4,000 characters per line. You may check a plan without SQL.

Looking for an example? Open SQL Syntax Reference.

Coverage and quoting assumptions

Oracle has no full grammar parser here. Its checks cover selected structural patterns, quotes, identifiers and common mistakes; PL/SQL checks are limited to lexical and basic block balance checks.

Other dialects use a third-party parser. Parser acceptance covers that library’s grammar, not every server feature. Rejections appear as Parser warnings because valid vendor syntax may be unsupported. SQLite bracket identifiers and empty IN lists, T-SQL omitted-name qualification and procedural/batch input fall back to lint only.

Assumes standard PostgreSQL strings, T-SQL QUOTED_IDENTIFIER ON, and MySQL’s default backslash escapes. MySQL ANSI_QUOTES and other SQL modes are not inferred. PostgreSQL dollar quotes and Oracle alternative strings are recognized. No schema is inferred.

About this tool

Syntax checks cannot establish that a table or column exists, types are compatible, permissions or constraints allow a change, or the query gives the intended business result. Parser grammars cover subsets of their databases; Oracle uses lint only.

Example: List the names and prices of shop products costing more than 20. Add a comma after price in the SELECT list to try a fixable syntax error.