Resources Exceeded Error

[Surekha_PM]

Hi Everyone,

I am using a star schema where one table is connected with 6 tables. There are also 2 calculated tables, which are the split of another table to check two different categories. There are also 2 calculated tables for date. One has the calendar date, and another is for date duration, like yesterday, last 30 days, etc. Now when I am trying to create the table, I am getting this error. There are no complicated calculations, and there are only 40000 rows of data overall. I am pasting the details below. Can anyone please help with this?
Error:

Data Model

Can anyone suggest anything to fix the issue.

Regards,
Surekha

[v-tsaipranay]

Hi @Surekha_PM ,

Thank you for the update, and I’m glad to hear the issue is now resolved. Please feel free to reach out to the Fabric Community. We’re always happy to help.

[v-tsaipranay]

Hi @Surekha_PM ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by @EsraaKamal , @rohit1991  and @srlabhe . If you still require support, please let us know, we are happy to assist you.

Thank you.

[Surekha_PM · Accepted solution]

Hello @EsraaKamal, @rohit1991, @srlabhe and @v-tsaipranay,

I appreciate how quickly you responded and provided a solution.

I tried every solution, but none of them were able to fix the problem. This is because the problem with my data set was different. Two date tables that I was using had non-continuous dates. The data load issue was resolved after those tables were removed.

Again, thank you very much for your support, everyone.

Regards,
Surekha 

[EsraaKamal]

Hi @Surekha_PM ,

The "Resources Exceeded" error on a dataset of only 40,000 rows confirms that this is not a data volume issue, but a Data Modeling issue. Even with millions of rows, Power BI usually handles star schemas easily. When it crashes on 40k rows, it is almost always due to "Table Ambiguity" or "Bi-directional Filtering" causing the engine to run a calculation that spirals into infinity (a massive Cartesian product).

Steps to resolve:

1. Strictly enforce Single Direction filters: Change all relationships to "Single" (One-to-Many) where the Dimension filters the Fact table.
2. Fix the Duration Table: Remove the Many-to-Many relationship if possible.
3. Hide Unused Keys: In the report view to prevent accidental usage in visuals, which can trigger bad query plans.

Hope this helps

[srlabhe]

I would suggest you to denormalize the dims and facts , may be try creating views out of it and use those in PBI.It seems your query is travelling across many combinations of relationships and joins and hence the error.

[Safaa]

But how you do denormalize

[EsraaKamal]

Option1: Instead of having Category A, C, and D as separate tables, combine them into one (Append Queries). And ensure to have a column in this unified table called "Category" or "Type" so you we can distinguish between them in visuals.

Option2: Can merge some of dimension fields (like City Name) directly into your Fact table. This allows you to delete the relationship lines entirely as it removes the join overhead.

I hope now its clear for you @Safaa 

[rohit1991]

Hii @Surekha_PM 

This error isn’t caused by your 40k rows but by the visual creating a very large intermediate join across many dimension tables, especially with calculated date tables. When too many fields from different tables are combined, Power BI can’t optimise the query and hits the “Resources Exceeded” limit. Try reducing the number of columns in the table visual, filter the date range, and avoid using calculated tables as dimensions. Once the visual has fewer cross-joins to perform, the error will disappear.

[AntoineW]

Hi @Surekha_PM,

The “Resources Exceeded” error usually appears when Power BI detects that a query requires too much memory or CPU because the model structure forces expensive operations — even if the dataset is small (40k rows is not an issue by itself).

Looking at your model, there are a few likely causes and ways to fix them:

---

✅ 1. Too many bi-directional or ambiguous relationships

Your schema shows several tables connected in multiple directions.
When a visual runs, Power BI must resolve filter propagation across all paths — this can trigger:

• relationship ambiguity

• large auto-exist operations

• expensive cross-joins

• excessive memory usage

➡ Fix

• Switch relationships to single-direction wherever possible

• Keep a clear separation: dimension tables → fact table (one direction)

• Avoid bi-directional or many-to-many relationships unless absolutely necessary

---

✅ 2. Too many calculated tables — computed at query time

You mentioned 4 calculated tables, including date tables and split versions of existing tables.

Calculated tables are stored but their logic is executed during model load and sometimes referenced at query time, which can increase memory pressure.

➡ Fix

• Replace calculated tables with Power Query transformations

• For date ranges (last 30 days, yesterday, etc.), use DAX measures, not calculated tables

---

✅ 3. A “snowflake” or circular filtering design

Your screenshot shows multiple fact-like tables linking with multiple dimensions, creating complex filter paths.

This is a typical scenario where visuals explode into large intermediate joins, even with small data volumes.

➡ Fix

• Simplify the schema to a proper star model

• Avoid dimension → dimension chains

• Merge small lookup tables in Power Query if possible

Even though your dataset is small (40k rows), the relationship logic can make Power BI behave like it’s processing millions, because the engine tries to resolve every possible combination.

Optimizing the data model is the real fix here — not increasing capacity.

Hope it can help you !

Best regards,

Antoine

[FBergamaschi]

Hi @Surekha_PM 

without more information I cannot answer

What do you mean "simple calculations"? What do you mean 40.000 rows overall? In a single table? In all tables? 

When do you get the error? In what visual? How is the visual arranged?

FB