Why should SQL keywords be UPPERCASE in team style guides?

While SQL is case-insensitive, writing keywords in UPPERCASE (SELECT, FROM, WHERE, GROUP BY) provides instant visual separation between SQL syntax constructs and application-specific schema identifiers (table and column names), dramatically speeding up code scanning.

Should table names be singular or plural?

Modern industry style guides overwhelmingly standardize on plural table names (`users`, `orders`, `invoices`) because a table represents a relation (collection) of multiple entity records, while singular names (`user_id`, `order_id`) are reserved for foreign keys.

How should SQL linting be automated in CI/CD?

Integrate a headless SQL formatter and linter into your GitHub Actions or GitLab CI pull request pipeline. Any PR containing unformatted SQL fails the lint check, prompting the developer to run the formatter before merging.

Why is explicit AS aliasing required for column aliases?

Writing `SELECT user_name AS customer_name` makes developer intent unmistakable. Omitting `AS` (`SELECT user_name customer_name`) risks catastrophic bugs: if a developer accidentally forgets a comma between two columns, the second column silently becomes the alias of the first.

SQL Formatting

Building an Enterprise SQL Style Guide: Formatting Standards, Linting, and Team Conventions

By Sharon Ben-Moshe · October 13, 2026 · 2 min read

Sharon Ben-Moshe is the founder of sqlfmt, a browser-based SQL formatter and validator with misspelled-keyword suggestions across PostgreSQL, MySQL, SQLite, SQL Server, and BigQuery.

The complete blueprint for an enterprise SQL style guide. Standardize formatting, keyword casing, indentation, naming conventions, and CI linting.

Quick answer

An enterprise SQL style guide establishes universal code conventions across an engineering organization: standardizing uppercase keywords, 2-space indentation, snake_case table and column identifiers, explicit AS aliases, and modular CTE structure. Automated linting in CI pipelines and pre-commit hooks enforces these standards automatically, eliminating style debates during pull request code reviews.

Key takeaways

Enforce UPPERCASE keywords (SELECT, FROM, WHERE) for rapid visual parsing.

Standardize on 2-space indentation and left-aligned major query clauses.

Always require the AS keyword for column aliases to prevent missing-comma aliasing bugs.

Automate enforcement via Git pre-commit hooks and CI/CD pull request status checks.

The 8 enterprise formatting rules

Uppercase Keywords: Write all SQL keywords, clause names, and core functions in UPPERCASE.

snake_case Identifiers: All table names, column names, schemas, and views must use lowercase snake_case.

Plural Table Names: Tables represent collections of rows; name them in the plural (e.g. accounts, payments).

2-Space Indentation: Indent clause bodies 2 spaces deeper than the clause keyword.

One Column Per Line: Place each projected column expression on its own line for clean git diffs.

Mandatory AS Aliasing: Never declare column aliases without the explicit AS keyword.

Leading Boolean Operators: Place AND and OR operators at the beginning of subsequent lines in WHERE and HAVING clauses.

CTEs Over Nested Subqueries: Structure complex multi-step transformations into named CTEs at the top of the query.

Enterprise-compliant SQL query reference implementation

-- Gold-standard enterprise formatted SQL query
WITH active_subscriptions AS (
  SELECT
    customer_id,
    plan_tier,
    started_at
  FROM billing.subscriptions
  WHERE status = 'active'
    AND canceled_at IS NULL
),
customer_spending AS (
  SELECT
    customer_id,
    COUNT(id) AS completed_orders_count,
    SUM(total_amount) AS lifetime_spent
  FROM core.orders
  WHERE status = 'completed'
  GROUP BY customer_id
)
SELECT
  c.id AS customer_id,
  c.email AS customer_email,
  s.plan_tier,
  COALESCE(cs.completed_orders_count, 0) AS completed_orders_count,
  COALESCE(cs.lifetime_spent, 0.00) AS lifetime_spent
FROM core.customers c
INNER JOIN active_subscriptions s
  ON c.id = s.customer_id
LEFT JOIN customer_spending cs
  ON c.id = cs.customer_id
WHERE c.is_verified = true
  AND c.deleted_at IS NULL
ORDER BY lifetime_spent DESC;

Building an Enterprise SQL Style Guide: Formatting Standards, Linting, and Team Conventions

Quick answer

FAQs

Why should SQL keywords be UPPERCASE in team style guides?

Should table names be singular or plural?

How should SQL linting be automated in CI/CD?

Why is explicit AS aliasing required for column aliases?

The Master Guide to SQL Common Table Expressions (CTEs): Syntax, Optimization Fences, and Recursion

How to Format Recursive CTEs in SQL: Hierarchical Query Structure

Formatting SQL Parentheses: Boolean Logic Precedence and Readability

Key takeaways

The 8 enterprise formatting rules

Automating enforcement in CI/CD pipelines

Official references

Quick answer

FAQs

Why should SQL keywords be UPPERCASE in team style guides?

Should table names be singular or plural?

How should SQL linting be automated in CI/CD?

Why is explicit AS aliasing required for column aliases?

Keep reading

The Master Guide to SQL Common Table Expressions (CTEs): Syntax, Optimization Fences, and Recursion

How to Format Recursive CTEs in SQL: Hierarchical Query Structure

Formatting SQL Parentheses: Boolean Logic Precedence and Readability

Key takeaways

The 8 enterprise formatting rules

Automating enforcement in CI/CD pipelines

Related SQL guides

Official references