DatriseAI-first ETL

k6 Cloud to Azure Synapse Integration

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

How Datrise loads k6 Cloud into Azure Synapse

Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times 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

k6 Cloud: Load testing runs and performance thresholds.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How k6 Cloud entities map to Azure Synapse

k6 Cloud entityAzure Synapse objectNotes
test runsk6_cloud_test_runsid PK · custom fields → NVARCHAR(MAX) JSON columns
thresholdsk6_cloud_thresholdsid PK · linked to k6_cloud_test_runs
checksk6_cloud_checksid PK · linked to k6_cloud_test_runs
metricsk6_cloud_metricsid PK · linked to k6_cloud_test_runs

FAQ

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