PBI Error : There's not enough memory to complete this operation.

[Anonymous]

I am working on PBI desktop report of ((600k rows, 8 colums) main dataset imported) and facing following error :

There's not enough memory to complete this operation. Please try again later when there may be more memory available.

System Specifications are as follows :

Processor : Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz 2.30 GHz

Insatlled RAM : 16.0 GB (15.6 GB usable)

System type : 64-bit operating system, x64-based processor

Windows Spec : 

Edition Windows 10 Enterprise
Version 21H2

PBI settings :

Auto date/time for new files is off.

Data Cache : 8000 MB

[Anonymous]

Hi @Anonymous ,

Have you resolved the issue now? What operation are you doing when such an error is reported? Publish the  report to the Service? Or create a column?

I have also found a similar post, please refer to it to see if it helps you.

Not enough memory to complete this operation - column creation 

• Replicate you calculation in Query Editor or check in Task Manager your memory behavior when you trying to calculate this column.

Extensive memory consumption causing problems and errors 

•  simply by deleting memory consuming parts of the report until refresh started working again.  Look for a way to make this less memory intensive.

If it is possible, please provide your pbix file without privacy information and more details.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hello,

 I'm having an issue with performance with one of my Calculated Columns.

I am trying to find the Train Run boarded by passenger

It does calculate correctly, but then I try to use this formula on production model it returns error that there is not enough memory to calculate. I suppose there should be a way to make this calculation more optimized.

IF( OD_Transaction_data[Interchange_Status] = 0,

Var identified_time = Calculate (FIRSTNONBLANK(Timetable[Time],-1),

FILTER(All(TimeTable),

TimeTable[#Station_Route]= OD_Transaction_data[StartStation_Route] &&

TimeTable[Time] >= (OD_Transaction_data[OD_startTime] + OD_Transaction_data[Movement time]/86400)&&

TimeTable[Direction] = OD_Transaction_data[Start Direction] &&

Timetable[Weekday] = OD_Transaction_Data[OD_StartDay]))

Var identified_run = CALCULATE(FIRSTNONBLANK(Timetable[Run],-1),

Filter(all(TimeTable),

TimeTable[Time] = identified_time &&

TimeTable[#Station_Route]= OD_Transaction_data[StartStation_Route] &&

TimeTable[Direction] = OD_Transaction_data[Start Direction]&&

Timetable[Weekday] = OD_Transaction_Data[OD_StartDay]))

Return identified_run,

Var identified_time = Calculate (FIRSTNONBLANK(Timetable[Time],-1),

FILTER(All(TimeTable),

TimeTable[#Station_Route]= OD_Transaction_data[EndInterchange_station_route] &&

TimeTable[Time] >= (OD_Transaction_data[OD_endTime] - OD_Transaction_data[Movement time]/86400 - OD_Transaction_data[MetroJourneyTime_Interchange_to_EndStation]/86400)&&

TimeTable[Direction] = OD_Transaction_data[Start Direction] &&

Timetable[Weekday] = OD_Transaction_Data[OD_StartDay]))

Var identified_run = CALCULATE(FIRSTNONBLANK(Timetable[Run],-1),

Filter(all(TimeTable),

TimeTable[Time] = identified_time &&

TimeTable[#Station_Route]= OD_Transaction_data[EndInterchange_station_route] &&

TimeTable[Direction] = OD_Transaction_data[Start Direction]&&

Timetable[Weekday] = OD_Transaction_Data[OD_StartDay]))

Return identified_run)

All filters are on numeric field route, direction, weekday - whole number

time (calculated to seconds) - Decimal

[Fowmy]

@Anonymous 

One issue that could cause performance is  ALL ( TimeTable ) Do not filter the whole table, filter only columns you need. 

[Fowmy]

@Anonymous 

check on the task manager to find out what consumes your memory. You can also check your Power BI file to find out if there are memory-heavy table creations are loaded (Calculated Tables).