SFTP Bulk to Amazon Redshift Integration

How Datrise loads SFTP Bulk into Amazon Redshift

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats into Amazon Redshift as a typed table per source entity. Flexible or custom fields land in SUPER columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMPTZ.

Sync is incremental: Datrise uses COPY from staged files, then a delete-and-insert merge on stable id, so re-runs update only what changed. A DISTKEY on the join id and a SORTKEY on the load timestamp. Redshift performance hinges on dist/sort keys, so Datrise picks them from your entity ids and sync timestamps rather than defaulting to EVEN distribution.

Ideal for AWS-native warehouses already using the Redshift ecosystem.

Endpoints

SFTP Bulk: Bulk file drops delivered over SFTP.

Amazon Redshift: AWS petabyte-scale warehouse with Spectrum.

How SFTP Bulk entities map to Amazon Redshift

SFTP Bulk entity	Amazon Redshift object	Notes
files	`sftp_bulk_files`	id PK · custom fields → SUPER 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 Amazon Redshift?

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

How does the SFTP Bulk to Amazon Redshift sync stay up to date?

It runs incrementally — Datrise uses COPY from staged files, then a delete-and-insert merge on stable id.

Related pipelines

Early access

Connect SFTP Bulk to Amazon Redshift 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.