The BigQuery query console

Run read-only GoogleSQL with a dry-run estimate, a byte cap on every job, script support and per-statement cost figures.

The BigQuery console runs GoogleSQL with syntax highlighting and autocomplete. Its banner states the model: a free estimate before running and a byte cap on every job.

The estimate

Before a query runs, Tablyne does a dry run and shows “will read” with the bytes and, on on-demand billing, an approximate cost. The estimate may be exact, an upper bound, a lower bound or unknown, and the console labels which. You can also ask for the dry run alone, which runs nothing and costs nothing.

  • Under the cap, the query runs.
  • Above the cap, Tablyne asks you to raise the cap for that run only.
  • With no estimate, which can happen with row-level security, the cap still applies and the server stops a query that goes over.
  • With an incomplete estimate, the console asks before it runs.

Only a SELECT, as the server classifies it, runs. If BigQuery does not report the statement type, Tablyne does not run it.

Tab context and scripts

Each tab has its own default dataset and job location. Fully qualified names do not depend on them.

Several statements, or DECLARE, IF and LOOP blocks, run as one script with one result per statement. A script always asks for confirmation, because the dry run only checks up to the first IF, WHILE or FOR. Tablyne adds up the billed bytes of the child jobs and cancels the script when it passes the cap. It sees a statement’s cost only after that statement finishes, so it can pass the cap by up to one statement. EXECUTE IMMEDIATE, CALL and transactions are not supported.

After the run

Each statement shows its time, bytes processed, bytes billed, slot time and approximate cost. A result from cache is marked as costing nothing. A plan view shows the stages of the last run. A daily spend warning can be set on the connection. It never blocks, and it asks you to confirm when the day’s total would pass it.