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
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v1 hour agoCommunity ChampionNew606Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v8 hours agoCommunity ChampionNew12Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019712 hours agoFrequent VisitorNew6Views0likes0Comments