OriginUse the query Workbench
Use the current console guide for live instance workflows and availability. Screenshots below illustrate the demo workspace with sample data. In the signed-in console, actions operate on the selected instance when your role and its capabilities allow them.
Write queries, inspect results, and keep useful drafts together in one instance workspace.
1. Open an instance workspace
Select an instance, then open Workbench in the sidebar. The page keeps the editor, results, and query library together. The tabs above it switch between Editor, Query stats, and Slow queries.
2. Choose what to explore
The library selector opens Explorer, Saved, or History. Explorer shows fields and example data for the selected query mode. Use its search field to find a table or field.
The editor's modality selector offers SQL, Vector, Full-text, and Graph. Each mode has its own input: SQL text, a query vector, search terms, or a graph traversal form. Start with Examples when trying a mode for the first time.
3. Keep related queries in tabs
Use New query to open a draft. The query-options menu can rename or duplicate it. Each tab retains its mode and input; an unsaved indicator marks changes. Closing an unsaved tab offers Save and close, Discard draft, or Cancel.
The preview keeps up to 20 open query tabs per instance. Query drafts belong to the selected organization and instance in this browser.
4. Run and inspect results
Click Run to execute the current input. The results area offers the formats relevant to that mode: a table, JSON, ranked matches, or a graph. Select a record to inspect its fields, or export the returned records as CSV.
For SQL, the arrow beside Run opens Explain plan and Explain and run. The first inspects a plan without executing the query; the second executes it. A returned plan appears under Query plan beside Results.
Plans in the local preview are schematic. Browser duration and illustrative operator values must not be read as live engine telemetry.
5. Save a query or revisit a run
Click Save to add a query to the Saved library. History records recent executions and lets you reopen their inputs. Opening an entry prepares a draft; it does not execute it.
The preview stores up to 100 saved queries and 100 history entries locally. They do not sync between machines, and clearing browser storage removes them. A saved query is a bookmark, not a scheduled job.
6. Check the target before running
The instance name in the workspace header identifies the current target. Use Connect for connection instructions, and check whether the page is showing local sample data or a live connection. Keep a LIMIT on exploratory SQL queries; the browser displays only the records returned to it.
Continue in your application
Move a working query into an SDK or the HTTP API when you need application credentials, bound inputs, or repeatable execution. Use query plans and diagnostics to investigate costly work.