Microsoft SQL Server to Holistics Integration

How Datrise loads Microsoft SQL Server into Holistics

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Microsoft SQL Server: Microsoft SQL Server transactional databases.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Microsoft SQL Server entities map to Holistics

Microsoft SQL Server entity	Holistics object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → flattened columns for the modeling layer
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 Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

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

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

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