Execution & cancellation
functionalRun the statement you mean to run, then stop it cleanly when the plan changes.
Run the whole document or only the selected statement,
then cancel a runaway query for real instead of merely looking away from it. Multiple
result sets arrive as separate grids, with errors, PRINT output, and
timing in the messages pane.
On SQL Server and Azure SQL the messages pane reads like SQL Server Management Studio: PRINT output and informational RAISERROR text (severity 10 or lower) appear as the server sent them, in order with your result sets, and every statement adds its “(N rows affected)” line, including statements inside stored procedures. SET NOCOUNT ON hides the counts, and severity 11 and above is still reported as an error.
- Run all executes every batch in order.
- Run selection executes only the highlighted text, useful in a scratch file full of statements.
- Cancel - ⌘Esc on macOS, Shift+Esc on Windows and Linux (Ctrl+Esc belongs to the Start menu) - asks the engine to stop the running statement: PostgreSQL's cancel protocol, SQLite's and DuckDB's interrupt, MySQL's and ClickHouse's
KILL QUERY, SQL Server's best-effortKILL, Oracle's client-side break, and an immediate stop on Redis. libSQL / Turso is the one exception, its server cannot interrupt a running statement, so Cancel abandons the request. A cancelled query stops burning server resources instead of continuing invisibly.
What happened, in one line
Every run ends with a one-line summary in the status bar, how many statements ran, rows returned, rows affected when any statement changed data, and the elapsed time, such as “3 statements · 128 rows affected · 0.42 s”. A failure shows the server's actual error text, and a stopped query says an honest “Query cancelled” rather than a generic “completed with errors”.
While a query is in flight, its tab shows a small accent dot beside the title, so you can switch to another tab and still see at a glance which one is busy.

