K6 Cloud → Azure Synapse
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 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
K6 Cloud: SaaS or API data source for analytics and warehouse sync.
Azure Synapse: Microsoft analytics workspace with SQL pools.
How K6 Cloud entities map to Azure Synapse
| K6 Cloud entity | Azure Synapse object | Notes |
|---|---|---|
| records | k6_cloud_records | id PK · custom fields → NVARCHAR(MAX) JSON columns |
| events | k6_cloud_events | datetime2 events |
| configuration objects | k6_cloud_configuration_objects | id PK · linked to k6_cloud_records |
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
More destinations for K6 Cloud
More sources for Azure Synapse
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.