SQL Formatter for BI Developers — Tableau, Power BI, Looker

BI developers writing SQL for Tableau, Power BI, Looker, or Sigma face a specific problem: the SQL editors built into BI tools are minimal. Tableau Custom SQL is a plain textarea. Power BI's DirectQuery editor is barely better. Looker has a SQL Runner but no format button. The result: BI devs end up with messy SQL embedded in dashboards that nobody can maintain.

Our browser tool covers the BI-specific use case. Format SQL before pasting into Tableau Custom SQL, Power BI DirectQuery, or Looker SQL Runner. Pick the warehouse dialect, get clean output. No signup, no install.

BI Tool SQL Editors Are Minimal by Design

BI tools are designed for visualization, not SQL editing. The query editors built into them reflect this:

• Tableau Custom SQL — plain textarea, no syntax highlighting in older versions, no format button. The SQL gets squished into the data source dialog.
• Power BI Native Query / DirectQuery — basic editor, no format option. SQL pastes in as-is and stays however you wrote it.
• Looker SQL Runner — has syntax highlighting but no format button. The textarea is small, hard to navigate long queries.
• Looker LookML derived tables — SQL embedded in YAML LookML files. Edited in the Looker IDE, which has basic editing but no SQL format button.
• Sigma Computing — visual query builder primarily, SQL view is basic.
• Mode Analytics — better than most, has syntax highlighting, but no consistent format button.
• Hex notebooks — Python-friendly, SQL formatting is rudimentary.
• Metabase native query editor — basic, no format button.

The reason: BI tool vendors optimize for the analyst persona who writes simple SELECT statements via the visual builder. The minority of users writing complex Custom SQL are an afterthought.

What BI Developers Need That Generic Formatters Often Miss

BI developer SQL has specific patterns that need to format cleanly:

Long SELECT lists with 30-50 columns. BI queries pull dozens of attributes from wide fact tables. The formatter needs one column per line.

Complex CASE WHEN expressions. BI SQL is full of CASE WHEN for derived metrics, KPI flags, and bucket categorizations. These need readable formatting.

Heavy use of CTEs. Modern BI SQL uses WITH clauses to layer transformations. Each CTE needs visual separation.

Window functions for cohorts and rankings. ROW_NUMBER, RANK, LAG, LEAD, SUM OVER constructs are everywhere in cohort analysis. The formatter needs to break these across lines.

Date and time gymnastics. DATE_TRUNC, EXTRACT, INTERVAL, generate_series — date manipulation is constant in BI. Format these readably.

Pivots via CASE WHEN aggregates. Manual pivoting is common when the BI tool's pivot UI cannot handle the case. Each CASE expression needs its own line.

Multiple JOIN types. Star schemas have LEFT JOIN to dimensions, INNER JOIN to bridge tables, sometimes CROSS JOIN for date spines.

The browser tool handles all of these with the warehouse dialect setting.

How BI Developers Use the Browser Formatter

1. Write your query in the BI tool — Tableau Custom SQL, Power BI native query, Looker SQL Runner, Looker LookML derived table.
2. When the query gets complex enough to be unreadable, copy it.
3. Paste into the browser SQL formatter.
4. Set the dialect matching your data warehouse — Snowflake (use BigQuery), BigQuery, PostgreSQL (Redshift, Postgres), Standard SQL (Databricks), Transact-SQL (Synapse, SQL Server).
5. Set indent to 2 spaces — modern BI conventions match dbt style.
6. Toggle uppercase keywords on.
7. Click Format.
8. Copy and paste back into the BI tool, replacing the original query.
9. Verify the visualization still works — formatting should not change semantics, but always verify.

Sell Custom Apparel — We Handle Printing & Free Shipping

BI Tool-Specific Formatting Tips

Tableau Custom SQL: Tableau's Custom SQL editor is small and does not show line numbers. Format externally, paste back. Tableau wraps long lines visually but not the underlying SQL — your formatted version stays clean.

Power BI DirectQuery: The native query editor accepts pasted SQL. Format externally, paste in. Power BI sometimes adds its own wrapper (a SELECT around your query) for the visual layer, which you cannot format — but the inner query you wrote stays clean.

Looker SQL Runner: Format externally, paste in. The SQL Runner is for ad-hoc exploration; you do not deploy from there.

Looker LookML derived tables: These live in YAML files in your LookML project. Format the SQL outside, paste back into the YAML derived_table.sql: block. The LookML parser handles the formatted SQL fine.

Sigma: Sigma's SQL view has basic editing. Format externally, paste in.

Hex: Hex SQL cells have basic formatting. For complex queries, format externally and paste back. Hex preserves the formatting.

Mode Analytics: Mode has decent editing but no format button. Same workflow.

Metabase: Metabase native query editor has basic features. Format externally for complex queries.

Why Formatted BI SQL Matters for Long-Term Maintenance

BI dashboards live for years. The analyst who built the dashboard often leaves the company before the dashboard is retired. The next analyst who maintains it has to read the SQL and figure out what it does. Unformatted SQL makes this much harder than it should be.

Real scenarios from BI teams:

• "This dashboard breaks every quarter and we cannot figure out why" — often because the SQL is unreadable and the analyst maintaining it cannot see the date filtering logic.
• "This metric calculation is wrong but we are afraid to touch the SQL" — because the original SQL is a wall of text and nobody wants to risk breaking it.
• "We need to add one column to this dashboard" — and the SELECT list has 47 columns crammed onto 3 lines, so finding the right place to add becomes archaeology.

Formatting the SQL when you write it (or when you next touch it) saves hours of future work. The browser tool makes this trivial.

Other Browser Tools BI Developers Use

BI developers do a lot more than write SQL. These browser tools handle adjacent tasks:

JSON formatter — for inspecting JSON results from semi-structured columns. JSON Formatter.

SQL diff checker — for comparing two versions of a metric definition. SQL Query Diff.

CSV to JSON converter — for moving small data between BI tools. CSV to JSON.

Cron expression generator — for scheduled queries and dashboard refreshes. Cron Generator.

Frequently Asked Questions

Will Tableau accept SQL formatted by this tool?

Yes. Tableau Custom SQL accepts whatever text you paste in. Formatted SQL works identically to unformatted SQL — only the indentation differs. Tableau executes both the same way.

Does Power BI strip my formatting when I save?

Power BI preserves the SQL string you paste into the native query editor. Your formatted version survives saves and reopens. The auto-generated wrapper SQL Power BI adds for visualization is separate from your inner query.

Can I format Looker LookML derived tables?

Yes. The SQL inside the derived_table.sql block in your LookML file can be formatted externally and pasted back. The LookML parser handles formatted multi-line SQL correctly.

Should I format SQL before or after the BI tool wraps it?

Format the SQL you write — the inner query. The BI tool may add its own wrapper for visualization purposes, but your inner query stays formatted as you wrote it.

Does this work for Mode Analytics queries?

Yes. Copy the query from Mode, format in the browser, paste back. Mode preserves the formatting.