DatriseAI-first ETL

GitLab Azure Synapse

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

How Datrise loads GitLab into Azure Synapse

Datrise syncs GitLab's projects, merge requests, pipelines, issues, and deployment 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

GitLab: DevOps platform for repos, CI/CD, and issue tracking.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How GitLab entities map to Azure Synapse

GitLab entityAzure Synapse objectNotes
projectsgitlab_projectsid PK · custom fields → NVARCHAR(MAX) JSON columns
merge requestsgitlab_merge_requestsid PK · linked to gitlab_projects
pipelinesgitlab_pipelinesid PK · linked to gitlab_projects
issuesgitlab_issuesid PK · linked to gitlab_projects

FAQ

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