Support for Hybrid mode
In old versions of SSAS you could have parts of an In-Memory cube/tabular be read directly from a source via Direct Query, this was a great feature. One of the main reason to use Direct Query is that the table you are using doesn't fit in memory and one of the main reasons to use In-Memory is that the source is too slow. Limiting users to choose mode for a whole model is bad.
Please (re-)add support for a hybrid mode where some tables are In-Memory and others are Direct Query. This is important for huge Azure SQL DW solutions where the fact tables don't fit in memory and the larger dimensions would really take good advantage of being in memory instead of having to be joined/queried along with others in the database.
Great suggestion. It is on our radar!
João Carlos commented
Excellent idea. I would say more, the ideal is that it was possible to choose the storage mode by partition. So, for example, in a very large table, you could partition it and define the partition with more recent data as "In-Memory" and partitions with older data as "Direct Query".
Omar Mahmood commented
Did the radar break Microsoft? Hybrid mode would really help! @Azure AS PM Team, @Admin.
Joao Carlos commented
It would be great to be able to set DirectQuery or In-Memory by partition. For example, newer data could be on an in-memory partition (Hot Partition) and older data on the DirectQuery Partition (Cold Partition).
Lokesh Reddy commented
We now have this feature available in power bi named as composite models.
Can you also add the same to AAS which is the heart of power bi for enterprise BI?
John Klacynski commented
Agree hybrid makes a lot of sense . Unloading hot unused is another feature missing