DatriseAI-first ETL

Snowflake to DuckDB Integration

AI-first ETL from Snowflake into DuckDB. Governed entities, incremental sync, typed landing tables.

How Datrise loads Snowflake into DuckDB

Datrise syncs Snowflake's databases, schemas, tables, views, query history, and warehouses into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Snowflake: Cloud data platform with separated storage and compute.

DuckDB: In-process analytics database for fast local OLAP.

How Snowflake entities map to DuckDB

Snowflake entityDuckDB objectNotes
databasessnowflake_databasesid PK · custom fields → JSON or STRUCT columns
schemassnowflake_schemasid PK · linked to snowflake_databases
tablessnowflake_tablesid PK · linked to snowflake_databases
viewssnowflake_viewsid PK · linked to snowflake_databases

FAQ

How does Datrise handle Snowflake's custom fields in DuckDB?

Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.

How does the Snowflake to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect Snowflake to DuckDB the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.