Microsoft SQL Server to Neon Integration

How Datrise loads Microsoft SQL Server into Neon

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Microsoft SQL Server: Microsoft SQL Server transactional databases.

Neon: Serverless Postgres destination with branching and autoscaling.

How Microsoft SQL Server entities map to Neon

Microsoft SQL Server entity	Neon object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → jsonb columns
rows	`mssql_sql_server_rows`	id PK · linked to mssql_sql_server_tables
schemas	`mssql_sql_server_schemas`	id PK · linked to mssql_sql_server_tables
indexes	`mssql_sql_server_indexes`	id PK · linked to mssql_sql_server_tables

FAQ

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

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

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