DatriseAI-first ETL

Sendwithus to Azure Synapse Integration

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

How Datrise loads Sendwithus into Azure Synapse

Datrise syncs Sendwithus's templates, sends, customers, delivery events, versions, and drip campaigns 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

Sendwithus: Templated transactional email and A/B testing.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Sendwithus entities map to Azure Synapse

Sendwithus entityAzure Synapse objectNotes
templatessendwithus_templatesid PK · custom fields → NVARCHAR(MAX) JSON columns
sendssendwithus_sendsid PK · linked to sendwithus_templates
customerssendwithus_customersid PK · linked to sendwithus_templates
delivery eventssendwithus_delivery_eventsdatetime2 events

FAQ

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