SQL reference

Use the SQL workbench to query tables in your accessible catalog. Start with the complete name shown in Data explorer: connector.dataset.table.

SELECT order_id, country, revenue
FROM lake.uploads.orders
WHERE status = 'completed'
ORDER BY revenue DESC
LIMIT 100;

Here, lake is the connector, uploads is the dataset, and orders is the table. These are sample names: replace them and the columns with your own catalog entries. For PostgreSQL, the dataset is the schema; a table might be pg.public.customers.

SQL language

• SQL syntax reference: selecting columns, filters, joins, CTEs, grouping, windows, and combining results.
• Scalar functions: text, numbers, dates, nulls, and conversions.
• Aggregate functions: totals, counts, averages, grouped values, and conditional metrics.
• Complex values: working with nested source data and transfer types.
• Workbench compatibility: accepted statements and the function supported list.

FastBI extensions

• All 19 functions: calendar buckets, safe conversion, conditional aggregation, and ratios.
• Cross-source querying: combine connectors in one result.
• Cross-source examples: practical joins and source-side CTEs.
• Query Lake data: catalog resolution, permissions, and scan safeguards.
• Results and limits: result pages, transfers, types, and saved data.

Practical guides

Follow the query primer, function essentials, and business examples. Use troubleshooting when a query is rejected or results differ from expectations.

Execution and cost

FastBI validates the query, resolves your catalog tables, and plans execution. A connected database must also support the SQL sent to it. The workbench does not translate arbitrary provider-specific syntax.

An output LIMIT does not guarantee less scanning or less cross-source transfer. Review the execution plan and pricing examples before running a broad query.