SFTP Bulk to DuckDB Integration

How Datrise loads SFTP Bulk into DuckDB

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats 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

SFTP Bulk: Bulk file drops delivered over SFTP.

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

How SFTP Bulk entities map to DuckDB

SFTP Bulk entity	DuckDB object	Notes
files	`sftp_bulk_files`	id PK · custom fields → JSON or STRUCT columns
directories	`sftp_bulk_directories`	id PK · linked to sftp_bulk_files
rows	`sftp_bulk_rows`	id PK · linked to sftp_bulk_files
file batches	`sftp_bulk_file_batches`	id PK · linked to sftp_bulk_files

FAQ

How does Datrise handle SFTP Bulk'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 SFTP Bulk 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 SFTP Bulk 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.