Forum Discussion
Memory error: Memory Allocation failure.
I went into the query editor and removed as many columns as possible and the refresh started working again. Also, I received this nugget of wisdom from Support:
From a memory consumption perspective it is better to add columns in the report developer using the add new measure/column function for optimized performance.
I hope that this can help someone else.
Thanks!!!
Jim
I went into the query editor and removed as many columns as possible and the refresh started working again. Also, I received this nugget of wisdom from Support:
From a memory consumption perspective it is better to add columns in the report developer using the add new measure/column function for optimized performance.
I hope that this can help someone else.
Thanks!!!
Jim
Can you elaborate on what this means?
From a memory consumption perspective it is better to add columns in the report developer using the add new measure/column function for optimized performance.
I believe that this means that there is more of a memory drag when you create columns during the import vs. when you have all of your tables loaded.
I have a 110 table model including 2 tables that exceed 2 million rows. I am experiencing this error. I have tried so many different solutions and I want to avoid removing columns as much as possible since this model was created by our DBA team. I was wondering if anybody knows if an incremental refresh would help this.
Thanks!
