Unformatted SQL is a maintenance hazard. A single query stretching across 300 characters with no line breaks is hard to read in a code review, nearly impossible to debug in a log file, and a nightmare to modify six months later.
Before:
`<code>sql</p>
<p>select u.id,u.email,o.total,o.created_at from users u left join orders o on u.id=o.user_id where u.created_at>'2024-01-01' and o.status='completed' order by o.created_at desc limit 100</p>
</code>
After:
<code>sql
<p>SELECT</p>
<p>u.id,</p>
<p>u.email,</p>
<p>o.total,</p>
<p>o.created_at</p>
<p>FROM users u</p>
<p>LEFT JOIN orders o</p>
<p>ON u.id = o.user_id</p>
<p>WHERE u.created_at > '2024-01-01'</p>
<p>AND o.status = 'completed'</p>
<p>ORDER BY o.created_at DESC</p>
<p>LIMIT 100;</p>
</code>
The query is identical — the database doesn't care about whitespace. But the second version makes the joins, conditions, and selected columns immediately scannable.
The Code Review Argument
SQL in code reviews is often the most poorly reviewed part of a pull request. Reviewers skim past a wall of unformatted SQL because parsing its structure mentally is too much cognitive work. Formatted SQL gets reviewed properly because you can see at a glance which tables are joined, what the WHERE conditions are, and whether SELECT * is being used.
Indentation That Helps
Main clauses (SELECT, FROM, WHERE, ORDER BY) at the left margin. Selected columns indented one level. JOIN conditions indented under the JOIN. AND/OR conditions aligned with each other.
<code>sql
<p>SELECT</p>
<p>column1,</p>
<p>column2</p>
<p>FROM primary_table</p>
<p>LEFT JOIN secondary_table</p>
<p>ON primary_table.id = secondary_table.fk_id</p>
<p>WHERE condition1 = 'value'</p>
<p>AND condition2 > 0</p>
<p>ORDER BY column1 DESC;</p>
</code>
Common Mistakes
- Everything on one line — readable to no one, including you in three months
- No spaces around operators — WHERE id=5
vs WHERE id = 5 - Not aliasing tables — FROM very_long_table_name vlt JOIN another_table at
is far cleaner - Missing semicolons — causes silent failures in multi-statement scripts
Capitalisation
UPPERCASE keywords (SELECT, FROM, WHERE`) is the traditional style and makes keywords visually distinct from table/column names. Some modern teams prefer lowercase. Pick one and be consistent — mixing is worse than either.
Quick Formatting
You don't have to format SQL by hand. The SQL Formatter & Beautifier at SnappyTools handles MySQL, PostgreSQL, and Transact-SQL in the browser. Paste your query, click Format, copy the result. No account required.
Formatted SQL is professional SQL. It signals you thought carefully about the query — which is a reliable indicator that you also thought about whether it's correct and performant.
Originally published at https://snappytools.app/sql-formatter-beautifier/