Build SQL SELECT queries visually with table joins, WHERE clauses, GROUP BY, and ORDER BY.
SQL Query Builder composes a SELECT statement from choices instead of keystrokes: you pick the base table, tick the columns you want, add joins by naming the matching key columns on each side, then stack up WHERE conditions, GROUP BY, and ORDER BY. The finished statement appears as text you can copy into your own database client or application. The surprise is that the tool has no view of your data: table and column names are just text you type, so a misspelled column still builds a query that looks finished and only fails when you run it.
A concrete input and expected output from the current implementation.
Input
In the builder: base table 'customers', select columns customer_id, name, country; add an INNER JOIN to 'orders' on customers.customer_id = orders.customer_id; add a WHERE condition country = 'US'; order results by name ascending.
Expected output
SELECT customers.customer_id, customers.name, customers.country FROM customers INNER JOIN orders ON customers.customer_id = orders.customer_id WHERE customers.country = 'US' ORDER BY customers.name ASC;
The statement is the direct composition of the four clauses you set, in the order SQL requires: SELECT, FROM, JOIN, WHERE, ORDER BY. The value 'US' is emitted as a quoted string literal because it is text, and columns are qualified with their table name so the join cannot create ambiguous references.
You work through the page one clause at a time: choose the base table, check the columns to return, add each join as two tables plus the columns that must match, and build conditions from a column, an operator, and a value. Every change re-renders the statement, which is where you copy your result. Conditions added separately are combined with AND, and each clause keeps its required position in the final text.
The builder keeps WHERE and HAVING as separate condition builders, matching SQL's rule that WHERE filters rows before grouping while HAVING filters the groups that survive. If your conditions seem to match nothing, the usual cause is a NULL column: no 'equals' comparison against NULL can be true, so a missing value must be expressed with the IS NULL or IS NOT NULL operator instead.
No, not against your data. Nothing in the page connects to a database, so it cannot catch a mistyped column name, and it does not run the statement to confirm it returns what you expect. The names you type are the only source of truth, so treat the result as a draft and execute it in your own client to verify it.
Most likely a NULL somewhere: a condition built with 'equals' can never match a column that holds NULL, because NULL is not a value and fails every comparison. Rebuild that condition with IS NULL or IS NOT NULL. If the condition looks correct, re-check your join keys, since a wrong key column silently pairs the wrong rows.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.