DatriseAI-first ETL

Jira Azure Synapse

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

How Datrise loads Jira into Azure Synapse

Datrise syncs Jira's issues, sprints, projects, changelogs, and worklog events 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

Jira: Issue tracking for software and operations teams.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Jira entities map to Azure Synapse

Jira entityAzure Synapse objectNotes
issuesjira_issuesid PK · custom fields → NVARCHAR(MAX) JSON columns
sprintsjira_sprintsid PK · linked to jira_issues
projectsjira_projectsid PK · linked to jira_issues
changelogsjira_changelogsdatetime2 events

FAQ

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