SQL Formatting Standards for Development Teams

Inconsistent SQL formatting wastes time in code reviews and makes queries harder to debug. Here are standards your team can adopt today.

Keyword Casing

Choose uppercase or lowercase for SQL keywords and stick with it. Uppercase (SELECT, FROM, WHERE) is the traditional standard and improves visual scanning. Lowercase is increasingly popular and easier to type. What matters is consistency, not the choice itself.

Clause Alignment

Put each major clause on its own line: SELECT, FROM, WHERE, GROUP BY, ORDER BY, LIMIT. Indent continuation lines. This makes it easy to comment out a clause during debugging by toggling a single line.

Column Lists

For SELECT statements with more than three columns, put each column on its own line with a leading comma. Leading commas make diffs cleaner and it is easier to spot missing commas.

Subquery Formatting

Indent subqueries one level and use CTEs (WITH clauses) instead of nested subqueries when possible. CTEs are more readable and easier to test independently.

Join Formatting

Write JOINs on their own lines with the ON clause indented below. Always use explicit JOIN syntax instead of comma-separated tables with WHERE conditions. Be explicit about the join type — write INNER JOIN, not just JOIN.

Automated Enforcement

Use our SQL Formatter tool to auto-format queries before committing. Integrate a SQL linter into your CI pipeline. The goal is to remove formatting from code reviews entirely so reviewers focus on logic.