What is SQL Studio?

SQL Studio is a genuine SQL query engine that runs entirely inside your browser. You import a CSV, JSON, or XLSX file (or paste data, or receive it from another Data Workspace tool), and it becomes a queryable table — visible in the schema sidebar with its real column names — that you can write actual SQL against: filter it, join it against a second table, group and aggregate it, or edit it with INSERT/UPDATE/DELETE. There's no database server anywhere in this — the query engine is a small SQL parser and executor written specifically for this tool.

What is SQL Studio not?

It is not a connection to a remote or production database, and it never queries one — every table you see in the schema sidebar exists only in your browser's memory, built from a file you imported in this session. It is also not a full ANSI SQL implementation — subqueries, CTEs, window functions, and multi-table chained JOINs beyond a single JOIN aren't supported (the exact list is in the tool's "What's not supported" panel and the Limitations section below). Being upfront about both of these is more useful than a tool that quietly pretends to be something it isn't.

What can you do with it?

SELECT with WHERE, ORDER BY, GROUP BY, HAVING, LIMIT, and DISTINCT.
JOIN — one INNER or LEFT JOIN between two imported tables, matched on an equality condition.
Aggregate functions — COUNT, SUM, AVG, MIN, MAX — combined with GROUP BY.
Common functions — UPPER, LOWER, LENGTH, ROUND, ABS, CONCAT, TRIM, COALESCE.
INSERT, UPDATE, DELETE — genuinely mutate the in-memory table you're working with.
CREATE TABLE — start a new empty table with defined columns.

How importing works

Import a CSV, JSON (an array of objects), or XLSX file, and it's parsed into a table with real column names shown in the schema sidebar — so you always know what to write in your FROM and SELECT clauses without guessing. You can also arrive here already carrying data via "Open in SQL Studio" from CSV Studio or XML Studio, which hands the current table straight over without a manual re-export/re-import step.

Example, once customers and orders tables are imported:

SELECT c.name, SUM(o.amount) AS total_spent
FROM customers c
JOIN orders o ON c.id = o.customer_id
GROUP BY c.name
ORDER BY total_spent DESC;

Limitations

Subqueries and Common Table Expressions (WITH ... AS) are not supported.
Only a single JOIN per query is supported — no chained multi-table joins.
Window functions (OVER, PARTITION BY) are not supported.
No transactions — every statement runs immediately against the in-browser table, there's nothing to commit or roll back.
UNION, INTERSECT, and EXCEPT are not supported.
Very large imported files may be slow, since every table lives in browser memory for the session.

Privacy

Imported files and every query you run stay in your browser — nothing is uploaded to a server. Refreshing the page clears all imported tables, since nothing is persisted beyond your current session.

Frequently asked questions

Is this a real SQL database, or does it just look like one?

It's a real, working SQL query engine — a hand-written SQL parser and executor that runs entirely in your browser. It genuinely evaluates WHERE conditions, performs JOINs, computes GROUP BY aggregates, and mutates data with INSERT/UPDATE/DELETE against whatever table you've imported. It is not a connection to any external or production database — see "What is SQL Studio not" below for exactly what it doesn't do.

Where does the data I query actually come from?

From a file you import (CSV, XLSX, or JSON) or paste in, or from a table handed off from another Convertam Data Workspace tool (CSV Studio, XML Studio). Nothing is fetched from a remote server — the "tables" you query are entirely in your browser's memory for the duration of your session.

Does my data get uploaded anywhere when I run a query?

No — every query executes locally in your browser against the in-memory table. Nothing you import or query is sent to a server.

What SQL features are NOT supported?

Subqueries, Common Table Expressions (WITH), window functions, multiple chained JOINs, UNION/INTERSECT/EXCEPT, and transactions are not supported — see the "What's not supported" panel inside the tool for the current, exact list. This is a genuinely useful subset for real single/two-table analysis, not a full ANSI SQL engine.

Can I use SQL Studio to modify my original file?

INSERT, UPDATE, and DELETE modify the in-memory table you're querying, and you can export the result back to CSV or JSON — but the original file you imported is never touched. Nothing is written back to disk automatically.

What happens if my query has a syntax error?

You get a specific error message describing what SQL Studio expected and where, rather than a silent failure or generic "query failed."