Skip to content

Can Cube.dev or Timbr.ai provide an OLAP layer for Superset on MSSQL? #37571

@damodhar-admin

Description

@damodhar-admin

Bug description

We are using Apache Superset connected to MSSQL and want to enable OLAP-style analytics (dimensions, measures, drill-downs) on live data, without dumping or materializing data into separate tables.

Superset supports SQL-based reporting but lacks a native OLAP / semantic layer for governed metrics.
We are exploring whether Cube.dev or Timbr.ai can act as a semantic layer between Superset and MSSQL.

Can these tools define OLAP-style cubes on top of MSSQL tables/views and expose them to Superset via SQL, while keeping the data live and real-time?
Any community experience or recommended approach would be appreciated.

Thank you.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions