It's all about the answers!

Ask a question

QueryExpired solution recommendation

sam detweiler (12.5k6194201) | asked Jan 17 '14, 2:52 p.m.
edited Jan 17 '14, 4:40 p.m.
 a number of us have run up against the dreaded query expired problem

another recommendation not listed in the referenced article is to cache the data in the client pgm.

we have an app that is taking upwards of 30 minutes to go thru all the workitems in the query. (6700)
by changing the app to cache, the query elapsed time was reduced to 32 seconds.(getting one record at a time)
using the getPage() function the cache time dropped to 12 seconds. 

our app still takes 30 minutes to process. 

side question.. is there an explicit way to 'close' the query, rather than let it timeout?
(Set the result set object to null which 'should' force a discard)

sam detweiler commented Jan 17 '14, 3:11 p.m.

Or you have to up the query expiry time in CCM Advanced properties 

sam detweiler commented Feb 20 '14, 6:48 a.m.

we kept running into long timeout issues..

I changed the code to cache all the query results at the beginning of the program,
then work off the cache.. takes a little more memory..

time to cache 7500 workitems.. 12 seconds..

Be the first one to answer this question!

Register or to post your answer.