Summary info provided from BRAVO defers from the one from DAX STUDIO #803
Replies: 1 comment 4 replies
-
The difference in the total size you're observing is due to the way each tool calculates this value. Bravo calculates the total size by considering only the sizes of columns, including data size, dictionary size, and hierarchy size for each column. On the other hand, DAX Studio includes not only the sizes of columns but also the sizes of relationships and custom hierarchies (user hierarchies). In your case, 61.48 MB (DAX Studio) - 60.98 MB (Bravo) = 0.5 MB, which corresponds to the size of the relationships and user hierarchies in your model. Regarding the difference in the number of columns, could you let me know which version of DAX Studio you used to extract the VPAX file? |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm using v 1.0.8 and I've noticed that number of columns detected from the model is different from what I get in DAX Studio.
The file *.vpax imported in BRAVO is the one exported from DAX Studio
Example
Dax Studio :
Total Size in Memory: 61,48 MB
Tables: 20
Columns: 153
Bravo:
Total Size: 60,98 MB
Tables: /
Columns: 111 columns, 40 of which are not referenced within the model.
Actually I believe that 40 are not included in the 111, indeed 111+40 is 151 which is much closer to 153, but still 2 missing.
Also Total size is slightly different..
any of you guys know the explanation on those differences?
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions