VictorOps to Azure Synapse Integration

How Datrise loads VictorOps into Azure Synapse

Datrise syncs VictorOps's incidents, alerts, on-call schedules, teams, escalation policies, and acknowledgements 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

VictorOps: On-call rotation and incident alerting.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How VictorOps entities map to Azure Synapse

VictorOps entity	Azure Synapse object	Notes
incidents	`victorops_incidents`	id PK · custom fields → NVARCHAR(MAX) JSON columns
alerts	`victorops_alerts`	id PK · linked to victorops_incidents
on-call schedules	`victorops_on_call_schedules`	id PK · linked to victorops_incidents
teams	`victorops_teams`	id PK · linked to victorops_incidents

FAQ

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