ClickHouse query console

Run ClickHouse SQL with typed parameters, per-run settings, EXPLAIN variants, live progress, cancel and an Activity view.

The console highlights ClickHouse SQL and completes function names from the server’s own list. A banner reminds you that ClickHouse has no transactions and that ALTER … UPDATE and DELETE are asynchronous: accepted does not mean finished.

Parameters use the server’s typed syntax, such as {id:UInt64}. A parameter without a type is rejected, and the value is sent as a parameter, not pasted into the text. USE database changes the database for that tab only. Nothing changes on the server.

Per-run settings let you add up to 16 settings to a run. Tablyne checks each name and value against the server’s settings list. Only performance and read settings are allowed. Limits and read-only mode cannot be changed there.

Results show rows read, bytes and memory while the query runs, and the query ID can be copied. Cancel sends KILL QUERY to the server and reports whether the query had already finished or whether the server did not confirm. A result is capped at 100,000 rows and 16 MiB. If a query asks for an explicit FORMAT, the result is shown as text.

EXPLAIN comes in several forms. They show the plan with indexes, an estimate of parts, rows and marks, the execution pipeline, the plan with actions, the syntax tree, and the query as the server rewrote it. None of them runs the query.

The Activity view shows running queries, history from system.query_log, query insights sorted by total time, mean time, p99 latency, calls or rows, and merges in progress. If your user cannot read those system tables, the view says so and does not guess.

An INSERT … FORMAT with pasted data does not run in the console. Use Import for that.