Pagerduty to Azure Synapse Integration

How Datrise loads Pagerduty into Azure Synapse

Datrise syncs Pagerduty's incidents, services, schedules, escalation policies, log entries, and responders 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

Pagerduty: Incident response, on-call schedules, and escalation.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Pagerduty entities map to Azure Synapse

Pagerduty entity	Azure Synapse object	Notes
incidents	`pagerduty_incidents`	id PK · custom fields → NVARCHAR(MAX) JSON columns
services	`pagerduty_services`	id PK · linked to pagerduty_incidents
schedules	`pagerduty_schedules`	id PK · linked to pagerduty_incidents
escalation policies	`pagerduty_escalation_policies`	id PK · linked to pagerduty_incidents

FAQ

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