Tyntec SMS to Azure Synapse Integration

How Datrise loads Tyntec SMS into Azure Synapse

Datrise syncs Tyntec SMS's SMS messages, recipients, delivery reports, senders, countries, and message costs 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

Tyntec SMS: Global SMS delivery and message status callbacks.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Tyntec SMS entities map to Azure Synapse

Tyntec SMS entity	Azure Synapse object	Notes
SMS messages	`tyntec_sms_sms_messages`	id PK · custom fields → NVARCHAR(MAX) JSON columns
recipients	`tyntec_sms_recipients`	id PK · linked to tyntec_sms_sms_messages
delivery reports	`tyntec_sms_delivery_reports`	id PK · linked to tyntec_sms_sms_messages
senders	`tyntec_sms_senders`	id PK · linked to tyntec_sms_sms_messages

FAQ

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