Forum Discussion
Memory Allocation failure . Try simplifying or reducing the number of Queries
Hi, I've had a file in the service for quite a while now (over a year) and just recently I started getting the following error. I've made any big recent changes especially to the number of queri...
- Hi there
I am certain that the above could be created in Power Query
I would suggest starting to learn Power Query, it will help solve a lot of data challenges you might face.
And there is a lot of free and paid resources on the web for Power Query training and learning.
My problem is with the Power BI service, not the desktop version, so I don't think the second one applies.
I've reviewed my queries, and I don't really have anything that complex. Not to mention they've been working for a while. The only new thing, is I do use summarizecolumns to create a inventory snapshot table.
I guess I could try removing that... But I kind of need it.
Hi there
It could well be that when you are creating this table (if the underlying data is large) it could cause it to consume a lot of memory.
This is because when you create a calculated table inside the Power BI dataset this is uncompressed and can consume a lot of memory.
The reason it could work on your desktop is because you are only limited by the amount of memory on your desktop which could be 8 or 16 or 32GB of RAM (Memory), whilst in the Power BI Service it is limited.
If you remove the table and it refreshes try and re-create the table in Power Query, this will allow the table to be compressed before it goes into the Power BI dataset.
It could well be that when you are creating this table (if the underlying data is large) it could cause it to consume a lot of memory.
This is because when you create a calculated table inside the Power BI dataset this is uncompressed and can consume a lot of memory.
The reason it could work on your desktop is because you are only limited by the amount of memory on your desktop which could be 8 or 16 or 32GB of RAM (Memory), whilst in the Power BI Service it is limited.
If you remove the table and it refreshes try and re-create the table in Power Query, this will allow the table to be compressed before it goes into the Power BI dataset.
Ok, I have confirmed that it is a new created table causing the problem. But I confess I'm not that good with Power Query. The DAX I am using to create the table is
Inv Summary Col = SUMMARIZECOLUMNS('Item Value New'[Item Ledger Entry Quantity], 'Item Value New'[Posting Date], "Bal Qty", CALCULATE(SUM('Item Value New'[Item Ledger Entry Quantity]), FILTER(ALL('Item Value New'[Posting Date]), 'Item Value New'[Posting Date]<=MAX('Item Value New'[Posting Date] ) ) ), "Bal Cost", CALCULATE(SUM('Item Value New'[Cost Amount (Actual)]) , FILTER(ALL('Item Value New'[Posting Date]) , 'Item Value New'[Posting Date] <= MAX('Item Value New'[Posting Date] ) ) ) )Can I do that in power query?
- Hi there
I am certain that the above could be created in Power Query
I would suggest starting to learn Power Query, it will help solve a lot of data challenges you might face.
And there is a lot of free and paid resources on the web for Power Query training and learning.Ok, I will put learning power query after I'm done reading "The Definitive guide to Dax".
Thanks,