DatriseAI-first ETL

Rki Covid Azure Synapse

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

How Datrise loads Rki Covid into Azure Synapse

Datrise syncs Rki Covid'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

Rki Covid: SaaS or API data source for analytics and warehouse sync.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Rki Covid entities map to Azure Synapse

Rki Covid entityAzure Synapse objectNotes
recordsrki_covid_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventsrki_covid_eventsdatetime2 events
configuration objectsrki_covid_configuration_objectsid PK · linked to rki_covid_records

FAQ

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