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.
I have a .pbix that looks at our transactional data. It comes in 3 seperate tables all related by transaction number
What would be the most efficient structure performance wise?
I tried to look up some documentation or previous thread, but couldn't find anything. Could I just gauge it by creating all 3 and looking at .pbix size? Or any other tips?
Solved! Go to Solution.
Hi @Anonymous
Some tips.
Try and flatten your tables as much as possible. If you can do in 3 tables, what your source system has in 6 then you are on the right track. Extra columns aren't an issue but get rid of any column once you know you don't need it.
Calculations that need to cross relationships, especially on large tables, will have a noticeable hit on performance.
Avoid bi-directional relationships if possible.
Hi @Anonymous
Some tips.
Try and flatten your tables as much as possible. If you can do in 3 tables, what your source system has in 6 then you are on the right track. Extra columns aren't an issue but get rid of any column once you know you don't need it.
Calculations that need to cross relationships, especially on large tables, will have a noticeable hit on performance.
Avoid bi-directional relationships if possible.
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 |
---|---|
106 | |
94 | |
76 | |
62 | |
50 |
User | Count |
---|---|
147 | |
106 | |
104 | |
87 | |
61 |