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.
Sometimes, for some use cases, you want the same table to be available more than once in the model instead of using (in)active relations with USERELATIONSHIP. Eg. a Order Date and Shipping Date table.
You can do that by referencing a table (using PQ) or by creating calculated tables in DAX.
I wonder what is the most efficient approach regarding speed, size (memory) and refresh times?
Solved! Go to Solution.
@__Marc__
Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
@__Marc__
Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
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 |
---|---|
111 | |
94 | |
83 | |
66 | |
59 |
User | Count |
---|---|
151 | |
121 | |
104 | |
87 | |
67 |