DatriseAI-first ETL

Mssql SQL Server Yellowfin

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

How Datrise loads Mssql SQL Server into Yellowfin

Datrise syncs Mssql SQL Server's records, events, and configuration objects into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Mssql SQL Server: SaaS or API data source for analytics and warehouse sync.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Mssql SQL Server entities map to Yellowfin

Mssql SQL Server entityYellowfin objectNotes
recordsmssql_sql_server_recordsid PK · custom fields → flattened columns
eventsmssql_sql_server_eventsdate/time dimensions events
configuration objectsmssql_sql_server_configuration_objectsid PK · linked to mssql_sql_server_records

FAQ

How does Datrise handle Mssql SQL Server's custom fields in Yellowfin?

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

How does the Mssql SQL Server to Yellowfin sync stay up to date?

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

Related pipelines

Early access

Connect Mssql SQL Server to Yellowfin 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.