# Pascal SQL Warehouse

Source: https://www.trypascal.io/platform/sql-warehouse

Ask in SQL. Answer in business terms.

Query your business objects and datasets with SQL. Explore the result, inspect its source context, and return to the query that produced it.

## Capabilities

### Find the right dataset

Explore available business objects and data products with descriptions, schemas, and their source context close at hand.

### Write SQL with business meaning

Query shared object and dataset definitions. Reuse the organization’s understanding of customers, orders, and other business concepts.

### Respect the current access policy

Keep query access scoped to the actor and workspace. Apply the relevant record and field controls before results are returned.

### Understand the work a query requires

Inspect the available execution path and applicable limits. Make resource requirements part of the query decision.

### Keep a history you can follow

Return to prior queries and their recorded results. Trace the inputs and execution behind an analysis someone shares with you.

### Put the answer into the next step

Use query results in an investigation or a downstream workflow, with their source references and permissions still attached.

## Connected context

Query data from Data Infrastructure and shared business definitions from Ontology. Reuse useful queries in Data Pipelines, notebooks, dashboards, applications, and agent investigations.

- Business objects, datasets, schemas, and query views
- Warehouses, sessions, saved queries, and reusable metrics
- Query history, retained results, execution plans, and exports

## Controls and permissions

Queries use the current workspace and data permissions. An empty answer, denied access, and a failed query remain distinct. Saving, publishing, or exporting a result requires the appropriate separate action.

## Example

Operations asks which Tacoma loads are ready. The analyst opens the saved query and finds five ready loads and two blocked loads. Query history preserves the result for the next reviewer; shipment actions still follow their own approval process.

## Workflow

### Ask the operating question

- The saved query checks current telemetry and shipment-specific approval. Its purpose is precise: understand which loads are ready.

### Read the result in context

- Seven Tacoma inbound loads appear in the retained result: five ready and two blocked. Readiness in a query does not authorize tendering.

### Return through query history

- Open the saved execution and its result. The team can inspect the same answer later, with unavailable execution details clearly identified.

## Next steps

Bring the source data, the access it requires, and the result your team needs to inspect or share.

- [Contact sales](https://www.trypascal.io/contact)
- [Pascal Work](https://www.trypascal.io/solutions/pascal-work)