Memory error: Memory Allocation failure . Try simplifying or reducing the number of queries.

[patri0t82]

Hello, I have a solution in place for my company that's been working fine for over a month, but now I'm receiving this error. I have no idea what could be causing the problem, as there's not many queries to deal with. Might I have to limit the report to a rolling 30 days?

This could potentially be a big problem, any help would be GREATLY appreciated.

[timg]

Hi ,

Some basic steps that usually work are:

• Increase available memory (if you are for example working from a VM)
• Remove all unnecessary columns in the power query editor
• Allocate more memory in the data load option in power bi (options > data load)

Perhaps those could already help you solve the issue. If not, it would be helpful if you could show us a sample of your queries. Perhaps we can give some more pointers based on what we see there.

Best regards,

Tim

[patri0t82]

Hi timg, thanks for your response. I believe I understand what the problem is, but I'm also not sure how on earth I could solve it.

Someone here provided me an amazing solution that provides a time difference between two time stamps on two rows, based on certain criteria. Now that I'm up to over ~24,000 rows it seems to have become too much to handle.

This is basically the solution that was  provided:

Time on Site (Minutes) (Unique Identifier) =

IF (

'Gate Scans'[Transit Direction] = "Exit",

VAR aux_ =

CALCULATE (

MAX ( 'Gate Scans'[FieldDateTime] ),

ALLEXCEPT ( 'Gate Scans', 'Gate Scans'[Company], 'Gate Scans'[SBIID1], 'Gate Scans'[Trade] ),

'Gate Scans'[FieldDateTime] < EARLIER ( 'Gate Scans'[FieldDateTime] )

)

RETURN

IF ( NOT ISBLANK ( aux_ ), 24 * 60 * ( 'Gate Scans'[FieldDateTime] - aux_ ) )

)

I am able to refresh in the desktop app and then publish to PBI online, but the online app can't handle this much work. One of our thoughts was to try and recreate this solution in Excel (refreshed daily using Power Automate) and then query the Excel file from PBI desktop, relieving the strain. 

Would you happen to have any other suggestions?

[timg · Accepted solution]

Hi,

If I understand correctly you are currently creating the column that is causing the issue with dax. You could try and add this column in power query instead. Calculated (dax) columns are not compressed as well as computed (power query) columns. So this could potentially save you the needed resources. The duration.totext() function in power query can be used to calculate the time difference between two timestamps so this may be a good place to start.

Regards,

Tim

[patri0t82]

Thanks for this suggestion, I will reach out to someone in the general forum with regards to this.