DatriseAI-first ETL

PostgreSQL to Azure Synapse Integration

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

How Datrise loads PostgreSQL into Azure Synapse

Datrise syncs PostgreSQL's tables, rows, schemas, indexes, sequences, and replication slots 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

PostgreSQL: Self-managed PostgreSQL instances.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How PostgreSQL entities map to Azure Synapse

PostgreSQL entityAzure Synapse objectNotes
tableshp_postgres_tablesid PK · custom fields → NVARCHAR(MAX) JSON columns
rowshp_postgres_rowsid PK · linked to hp_postgres_tables
schemashp_postgres_schemasid PK · linked to hp_postgres_tables
indexeshp_postgres_indexesid PK · linked to hp_postgres_tables

FAQ

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