Forum Discussion
Dataset Refresh Fails with error : The evaluation reached the allowed cache entry size limit
hey, try reducing the number of simulstanious evaluation it does in addition to increasing the maximum MB permit per evaluation(that you aleady did).
also try to norrow down the query giving you the error you can run each query one by one and see the amount of time taking each one and the amount of data its pulling. them send over the query script to see if theres a optimization issue with the code.
if all fails also open a support ticket for microsoft since they can provide you additional information on the server error its giving you if you cant access any more information about the incident to determine (also try running each query as a dataflow to see how its behavite in the web service).
hope this give some orientation to start with
hey, try reducing the number of simulstanious evaluation it does in addition to increasing the maximum MB permit per evaluation(that you aleady did).
also try to norrow down the query giving you the error you can run each query one by one and see the amount of time taking each one and the amount of data its pulling. them send over the query script to see if theres a optimization issue with the code.
if all fails also open a support ticket for microsoft since they can provide you additional information on the server error its giving you if you cant access any more information about the incident to determine (also try running each query as a dataflow to see how its behavite in the web service).
hope this give some orientation to start with
Thank you very much for your response.
I reduced simultaneous evaluations but with no luck. I reduced the complexity (removed some merge steps) of some of the queries but still get the error.
Currently I am moving the queries to dataflows but it is considerable work.
I will come back with feedback later.Best
The answer was in "try running each query as a dataflow to see how its behavite in the web service". When I moved the queries on dataflows I was able to spot the query giving the error.
