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
Support Native SQL LIKE / NOT LIKE Wildcard Filtering Across Power BI Reports
Description Currently, Power BI does not provide a native way for report consumers to perform dynamic SQL-style wildcard filtering using patterns such as LIKE '____' - Above return all values wit...Seeralan37 minutes agoNew MemberNew3Views0likes0CommentsRetain Matrix/Table Scroll Position When Returning from Drillthrough
Description: Currently, when users drill through from a Matrix or Table visual to a detailed page and then use the Back button to return, the report navigates back to the source page but resets the ...Pruthviraj151 hour agoNew MemberNew8Views0likes0Comments