Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Solved! Go to Solution.
Hi , @Anonymous
Anyway you need to understand the composition and content of pbix first.
You can refer to this article (Here is a lot of what you want to know)
What makes up a powerbi desktop pbix file
exposing-m-code-and-query-metadata-of-power-bi-pbix-file
Best Regards,
Community Support Team _ Eason
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi , @Anonymous
Could you please tell me whether your problem has been solved?
If it is, please mark the helpful replies or add your reply as Answered to close this thread?
Best Regards,
Community Support Team _ Eason
Hi , @Anonymous
Anyway you need to understand the composition and content of pbix first.
You can refer to this article (Here is a lot of what you want to know)
What makes up a powerbi desktop pbix file
exposing-m-code-and-query-metadata-of-power-bi-pbix-file
Best Regards,
Community Support Team _ Eason
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hey @Anonymous ,
the number one point that determines the size of the data model is the number of unique values in each column, the more unique values, the larger the model.
You can inspect the data model, using the vertipaq analyzer, that can be found here:
https://www.sqlbi.com/tools/vertipaq-analyzer/
Since version 2.9.4 also DAX Studio can answer the questions of what structure exactly is responsible for the size of the data model: https://www.sqlbi.com/blog/marco/2019/09/15/vertipaq-analyzer-2-0-preview-1/
Why is the file size shrinking?
Due to creating a single table, you also reduce the number of columns, as there is no longer any need for 2 key columns (dimension and fact table). As there is just one table, there are no longer relationships, but from my experience relationships are never that big.
Please be aware that, a star schema is the design to go for, as a one-table solution might create unexpected results: https://www.sqlbi.com/articles/understanding-dax-auto-exist/
Regards,
Tom
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
110 | |
94 | |
80 | |
67 | |
59 |
User | Count |
---|---|
150 | |
119 | |
104 | |
87 | |
67 |