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
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande8 hours agoNew MemberNew180Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes17 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v17 hours agoCommunity ChampionNeeds Votes37Views2likes1Comment