Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
I'm currently facing a storage optimization challenge in Power BI and I'm seeking your advice on how to efficiently link two tables while minimizing data duplication. Here's a brief overview of my situation:
I have two tables in Power BI: Fact Table 1 and Table 2.
Fact Table 1 contains columns X, Y, Z, and X_Y_Z, which is the concatenation of X, Y, and Z and others columns:
| ... | X | Y | Z | X_Y_Z | ... |
| ... | 1 | 10 | 9 | 1109 | ... |
| ... | 2 | 20 | 8 | 2208 | ... |
| ... | 3 | 30 | 7 | 3307 | ... |
Table 2, on the other hand, has columns X, X_Y_Z and others columns:
| ... | X | X_Y_Z | ... |
| ... | 1 | 1109 | ... |
| ... | 2 | 2208 | ... |
| ... | 3 | 3307 | ... |
From a business point of view, I need to link fact table 1 and table 2 using using the combination that X Y Z generates. However, I also need to use columns X, Y, and Z separately to relate to other tables. Consequently, I find myself duplicating information and utilizing more storage for the same data.
As a result, my dataset is nearing its storage limit of 1GB, and I'm eager to optimize it as much as possible. Upon analyzing my model using tools like DAX Studio and vertipaq analyzer, I discovered that the X_Y_Z column alone occupies nearly half of my table's storage capacity.
Therefore, I would greatly appreciate your advice on how to approach this situation. How can I link Fact Table 1 to Table 2 using the combination of X, Y, and Z, while still enabling separate links with other columns? I'm open to suggestions and best practices to efficiently manage my storage space.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 50 | |
| 49 | |
| 35 | |
| 15 | |
| 14 |
| User | Count |
|---|---|
| 91 | |
| 75 | |
| 41 | |
| 26 | |
| 25 |