DatriseAI-first ETL

Pivotal Tracker Azure Synapse

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

How Datrise loads Pivotal Tracker into Azure Synapse

Datrise syncs Pivotal Tracker's records, events, and configuration objects 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

Pivotal Tracker: SaaS or API data source for analytics and warehouse sync.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Pivotal Tracker entities map to Azure Synapse

Pivotal Tracker entityAzure Synapse objectNotes
recordspivotal_tracker_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventspivotal_tracker_eventsdatetime2 events
configuration objectspivotal_tracker_configuration_objectsid PK · linked to pivotal_tracker_records

FAQ

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