As sad as it is, there needs to be focus on one way forward - that appears to be tabular. A migration path is needed, but having the two models is confusing and becoming unnecessary. Even if full support for MD features is not available I think this should still happen.
5 Comments
- pedro8New MemberThis is an extremely obtuse assertion. Multidimensional cubes are a different architecture which has its place in the enterprise and more often I find myself having to deploy both tabular and multidimensional models. Tabular has some advantages but it haves some serious limitations as well, and this is simply the way it is. In fact the more I use SSAS in tabular mode the more I find its limitations to be infuriating. One might as well say they want to deprecate pencils because of pens. If MSFT ever deprecated MD models they would be losing their competitive advantage to the likes of IBM and Oracle.
- Adrian_TheumaNew MemberI agree Pedro. I can't see this ever happening without Tabular first catching up to MD.
- fimianiNew MemberAgreed. There are a number of gaps that MD has that Tablular does not, and a few in the other direction as well. Tabular shortcomings when compared to MD: * write-back, * non-leaf writeback, * many-to-many, * unary operators, * several other critical things... Tabular upside compared to MD: * ability to on-the-fly model (add user-defined measures, dimension, granularities, hierarchies), * faster query times so I've heard, * other stuff? By no means an all-inclusive list. All that MS has to do is build out a gateway on top of MD that serves up the MD data as flattened Tabular slices, and there wouldn't be any issue here. Guess I'm just compelled to use Tableau until they get all of this resolved.
- pedro8New Member'@tf: Another serious limitation for me is the Direct query functionality of tabular models, which is meant to be analogous to ROLAP cubes. The fact is that when you turn direct query on, we get a severe set of limitations, which in my view makes Direct Query as useful as an ashtray on a motorbike :) For example we cannot use direct query when combining multiple data sources. This means that creating a tabular model to query line of business applications is inpractical since I cannot combine it with other data-sources, such as a date dimension from another DB.
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Add Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules
Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions. Activator rules can ...mourakshit1 minute agoNew MemberNew0Views0likes0CommentsPreserve Power BI Semantic Model Measures and Business Metadata When Generating Fabric IQ Ontologies
When Fabric IQ generates an ontology from an existing Power BI semantic model, it should preserve more of the business semantics that organizations have already invested in defining. Today, a semant...mourakshit7 minutes agoNew MemberNew1View0likes0CommentsEnforce OneLake Row and Column Security End-to-End in Fabric IQ Ontology
Fabric IQ Ontology should natively preserve and enforce OneLake Security when users access ontology entities, relationships, graphs, and downstream AI experiences. Enterprises may define row-level a...mourakshit9 minutes agoNew MemberNew1View0likes0CommentsSupport Schema Evolution for Fabric Graph Without Rebuilding the Graph Model
Fabric Graph should support controlled schema evolution as enterprise business models change over time. Graph models are rarely static. Organizations need to add new node types, properties, relation...mourakshit11 minutes agoNew MemberNew1View0likes0CommentsMake Fabric IQ Ontology Entities First-Class Assets in OneLake Catalog
Fabric IQ ontology entities and business concepts should be discoverable as first-class governed assets in OneLake Catalog. Today, users often need to know the underlying Fabric item, table, semanti...mourakshit13 minutes agoNew MemberNew1View0likes0Comments