DatriseAI-first ETL

MailerSend to Azure Synapse Integration

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

How Datrise loads MailerSend into Azure Synapse

Datrise syncs MailerSend's messages, templates, domains, delivery events, recipients, and bounces 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

MailerSend: Transactional email delivery and templates.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How MailerSend entities map to Azure Synapse

MailerSend entityAzure Synapse objectNotes
messagesmailersend_messagesid PK · custom fields → NVARCHAR(MAX) JSON columns
templatesmailersend_templatesid PK · linked to mailersend_messages
domainsmailersend_domainsid PK · linked to mailersend_messages
delivery eventsmailersend_delivery_eventsdatetime2 events

FAQ

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