The SQL console is the embedded SQL interface available within Foundry applications, providing contextual SQL access to the resource you are currently viewing. The SQL console is targeted for quick queries in the context of a specific resource (such as a dataset or object type). For a dedicated, full-screen SQL application, see SQL Studio.
You can access the SQL console in the bottom panel of supported applications:
| Application | Resources queryable |
|---|---|
| Dataset Preview | Tabular data |
| Data Lineage | Tabular data |
| Ontology Manager | Ontology object types and backing tabular data |
The starter query is prepopulated based on the resource you are currently viewing.

The SQL console provides core SQL editing and execution functionality, including running queries, autocomplete for tables and columns, an inline results panel, and the ability to save queries as SQL worksheets. The SQL console uses Foundry's Spark SQL dialect.
For full details on SQL features, including worksheets, AI-assisted query generation, and result visualization, see the SQL Studio documentation.
In Ontology Manager, the SQL console supports two modes:
When viewing an object type in Ontology Manager, you can select between modes from the mode dropdown in the SQL console toolbar. The object type's backing dataset is suggested as the default resource in data mode.

In other applications, only data mode is available.
To open the current query in a dedicated, full-screen application, select the expand option in the SQL console toolbar. This launches SQL Studio, which provides a full SQL application with a resource browser, version history, AI-assisted query generation, and additional capabilities not available in the embedded console.
A standalone full-screen view of the SQL console is temporarily available in environments where SQL Studio is not yet enabled. This standalone view will be replaced by the SQL Studio application.
Access to the SQL console is governed by the same SQL and download control roles that apply across Foundry. For details on the available roles and how they interact with SQL access, see SQL permissions.