Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
When I opne the PowerBI report I am getting the following Memory limit issue. May I know what could be the possible reason for this? I also having issues loading data to the visualizations as it takes very long to load data to visuals. I'm new to Fabric and may I know how I can rectify this issue.
Solved! Go to Solution.
You need a true star schema:
One or more dimension tables (Date, Customer, Product, etc.)
Each fact table connects only to dimensions
No fact-to-fact relationships
Example:
DimCustomer ──▶ Fact_A DimCustomer ──▶ Fact_B DimCustomer ──▶ Fact_C
Columns → from dimension tables
Values → measures from facts
Do NOT put fact columns directly into the table.
Instead of this (problematic):
Fact_A[Amount]
Fact_B[Cost]
Fact_C[Quantity]
Do this:
Amount A = SUM ( Fact_A[Amount] )
Cost B = SUM ( Fact_B[Cost] )
Qty C = SUM ( Fact_C[Quantity] )
Rows → dimension attributes
Values → these measures
This avoids row-level joins completely.
Make sure:
Single-direction filters from Dimension → Fact
Avoid Both unless strictly required
Avoid many-to-many unless unavoidable
Many-to-many + table visual = memory disaster.
Hi @dsrajapaksa ,
Thank you for reaching out to the Microsoft Community Forum.
Hi @cengizhanarslan , Thank you for your prompt response.
Hi @dsrajapaksa , could you please try the proposed solution shared by @cengizhanarslan ? Let us know if you’re still facing the same issue we’ll be happy to assist you further.
Regards,
Dinesh
Hi @dsrajapaksa ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh
You need a true star schema:
One or more dimension tables (Date, Customer, Product, etc.)
Each fact table connects only to dimensions
No fact-to-fact relationships
Example:
DimCustomer ──▶ Fact_A DimCustomer ──▶ Fact_B DimCustomer ──▶ Fact_C
Columns → from dimension tables
Values → measures from facts
Do NOT put fact columns directly into the table.
Instead of this (problematic):
Fact_A[Amount]
Fact_B[Cost]
Fact_C[Quantity]
Do this:
Amount A = SUM ( Fact_A[Amount] )
Cost B = SUM ( Fact_B[Cost] )
Qty C = SUM ( Fact_C[Quantity] )
Rows → dimension attributes
Values → these measures
This avoids row-level joins completely.
Make sure:
Single-direction filters from Dimension → Fact
Avoid Both unless strictly required
Avoid many-to-many unless unavoidable
Many-to-many + table visual = memory disaster.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |