Microsoft SQL Server to Yellowfin Integration

How Datrise loads Microsoft SQL Server into Yellowfin

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking 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

Microsoft SQL Server: Microsoft SQL Server transactional databases.

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

How Microsoft SQL Server entities map to Yellowfin

Microsoft SQL Server entity	Yellowfin object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → flattened 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 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 Microsoft 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 Microsoft 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.