Ok, so this is somewhat radical but if the engine teams want a challenge π ... The relational engine and tabular/power pivot all use in-memory tech. Tabular is basically a relational model with some computed columns (DAX) so, as a DW implementer, why am I having to land my data in the RDBMS and then re-process it into another in-memory store just because it talks a different language and protocol? It would be a big thing to be able to point an reporting tool e.g. Excel, Power BI (and yes, other vendors visualisation tools) straight at the relational db and get a SASS like experience. To be able to query the same store with either T-SQL or DAX (and MDX please) and get the latest loaded data without waiting for another processing step could be a game changer.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun β rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias6 hours agoRegular VisitorNew8Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu7 hours agoMicrosoft EmployeeNew9Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb9 hours agoNew MemberNew4Views0likes0Comments