SQLBuild uses adapters to connect to different database engines. Set the adapter inDocumentation Index
Fetch the complete documentation index at: https://docs.sqlbuild.com/llms.txt
Use this file to discover all available pages before exploring further.
sqlbuild_project.yml:
sqlbuild_local.yml:
DuckDB
DuckDB is included as a core dependency. No extra installation needed.Connection config
| Field | Description |
|---|---|
database | Path to the DuckDB database file. Use :memory: for in-memory databases. |
extensions | List of DuckDB extensions to install and load on connect. |
settings | Key-value pairs passed as SET statements on connect. |
attach | List of additional databases to attach. |
Extensions and settings
Attaching additional databases
Table promotion mode
DuckDB defaults tostaged promotion: tables are materialized into a staging table, audited, then swapped into the target. This is configurable in settings:
Snowflake
Snowflake requires the optionalsnowflake-connector-python dependency:
Connection config
connection are passed directly to snowflake.connector.connect(). See the Snowflake Connector documentation for all available options, including key-pair authentication, OAuth, and SSO.
Session initialization
On connect, SQLBuild runsUSE ROLE, USE WAREHOUSE, USE DATABASE, and USE SCHEMA statements based on the connection config. These ensure the session context is set correctly regardless of the user’s default settings.
Per-environment connections
Use environments to connect to different Snowflake databases or warehouses:Coming soon
- Databricks - install with
sqlbuild[databricks] - BigQuery - install with
sqlbuild[bigquery] - ClickHouse

