The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
If I copy a table (using ProjectData-DAX = 'ProjectData'), the resulting table is way bigger in terms of memory size than the original table. Why is this?
Screenshot VertiPaq Analyzer
Thanks in advance for your hints!
Solved! Go to Solution.
@Anonymous That's because SSAS uses sorting to reduce the size of the table, before loading the data into the model SSAS will find the best columns that will help in reducing how frequently the value changes, so if you have a column that has TRUE/FALSE and if that column is used first in the sort order, it will split the whole table into 2 chunks and the value will change only once, after that other columns will be used for sorting.
Once you load the data using DAX, the sorting doesn't occur but the columns are still compressed, so that's why the size of the table created with DAX can be biger.
@Anonymous That's because SSAS uses sorting to reduce the size of the table, before loading the data into the model SSAS will find the best columns that will help in reducing how frequently the value changes, so if you have a column that has TRUE/FALSE and if that column is used first in the sort order, it will split the whole table into 2 chunks and the value will change only once, after that other columns will be used for sorting.
Once you load the data using DAX, the sorting doesn't occur but the columns are still compressed, so that's why the size of the table created with DAX can be biger.
User | Count |
---|---|
28 | |
10 | |
8 | |
6 | |
5 |
User | Count |
---|---|
33 | |
13 | |
12 | |
9 | |
7 |