DatriseAI-first ETL

Redshift to Azure Synapse Integration

AI-first ETL from Redshift into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Redshift into Azure Synapse

Datrise syncs Redshift's tables, rows, schemas, sort keys, distribution keys, and query history into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Redshift: Columnar cloud data warehouse on AWS.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Redshift entities map to Azure Synapse

Redshift entityAzure Synapse objectNotes
tablesredshift_tablesid PK · custom fields → NVARCHAR(MAX) JSON columns
rowsredshift_rowsid PK · linked to redshift_tables
schemasredshift_schemasid PK · linked to redshift_tables
sort keysredshift_sort_keysid PK · linked to redshift_tables

FAQ

How does Datrise handle Redshift's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Redshift to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Redshift to Azure Synapse 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.