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
Disable auto-restore previous session's tabs in new Fabric sessions
Description: Since a recent update, starting a new Fabric session β for example by opening Fabric in a new browser tab β automatically reopens all the item tabs that were left open from a previous s...MathieuVr4 hours agoFrequent VisitorNew56Views5likes1CommentExported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev8 hours agoNew MemberNew12Views0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky9 hours agoNew MemberPlanned876Views15likes5Comments