Microsoft SQL Server to Redash Integration

How Datrise loads Microsoft SQL Server into Redash

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

Microsoft SQL Server: Microsoft SQL Server transactional databases.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Microsoft SQL Server entities map to Redash

Microsoft SQL Server entity	Redash object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → flattened columns for query results
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 Redash?

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

How does the Microsoft SQL Server to Redash 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 Redash 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.