Forum Discussion
Solved
Understanding the Vertipaq Engine
Hello I am doing a deep dive into the Vertipaq engine and I have a few questions regarding a concrete use case. I have a .pbix file with two Fact Tables: - Raw (300k rows and 17 columns) wit...
- Columns Hierarchies are internal structures storing a sorted textual version of the content of each column. It is required for MDX, and it is now used also internally for optimizing certain queries (in other words - we cannot get rid of it, even for columns we never use un MDX)
- See above - even numbers are converted into strings
- I don't understand the question - but VertiPaq Analyzer reports the memory consumption of the data model, whereas the size of the files could be different (serialization and additional structures).
I hope it helps!
Marco Russo - SQLBI
- Columns Hierarchies are internal structures storing a sorted textual version of the content of each column. It is required for MDX, and it is now used also internally for optimizing certain queries (in other words - we cannot get rid of it, even for columns we never use un MDX)
- See above - even numbers are converted into strings
- I don't understand the question - but VertiPaq Analyzer reports the memory consumption of the data model, whereas the size of the files could be different (serialization and additional structures).
I hope it helps!
Marco Russo - SQLBI
For the folks on this thread, there is a new 'Available in MDX' feature in Azure Analysis Services, SSAS 2017 (and soon Power BI Premium) which answers my questions n°1 and n°2 above: https://blog.crossjoin.co.uk/2018/07/02/isavailableinmdx-ssas-tabular/