DatriseAI-first ETL

Codat Microsoft SQL Server

AI-first ETL from Codat into Microsoft SQL Server. Governed entities, incremental sync, typed landing tables.

How Datrise loads Codat into Microsoft SQL Server

Datrise syncs Codat's records, events, and configuration objects into Microsoft SQL Server 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 a watermark on updated-at, applied with a MERGE statement, so re-runs update only what changed. Optional partitioned tables on a date partition function. SQL Server defaults to a case-insensitive collation, so Datrise preserves original casing in a metadata column to avoid silent key collisions.

Ideal for Microsoft-stack analytics and Power BI Import models.

Endpoints

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

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Codat entities map to Microsoft SQL Server

Codat entityMicrosoft SQL Server objectNotes
recordscodat_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventscodat_eventsdatetime2 events
configuration objectscodat_configuration_objectsid PK · linked to codat_records

FAQ

How does Datrise handle Codat's custom fields in Microsoft SQL Server?

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 Microsoft SQL Server types.

How does the Codat to Microsoft SQL Server sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with a MERGE statement.

Related pipelines

Early access

Connect Codat to Microsoft SQL Server 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.