I was primarily concerned with IRPQLSRV [related to my other question] as we have a dashboard hosting 2 weeks of intervals [1 hour, 336 intervals]. We are getting MEMORY LIMIT EXCEEDED and periodically losing the data.
Ok, hopefully the other suggestion takes care of it.
However, depending on what you have in the display, you may want to store that data in a prognosis database, so that even if someone navigates away from the display or pqlsrv crashes, you don't loose your data. This way, you can create a dashboard off the database.
If my reply answered your question please click on the 'Accept as Solution' button to help others find the answer. Thanks, Shoaib
The question originally came about though that I thought the 32-bit version of the process (and I may have been mistaken) had a 4096 memory limit associated with it and he was aware of the x64 path but remembered from Summit it being mentioned that some extra steps needed to be done to utilize those versions.
The dashboard Garrett mentioned needs to be realtime though so immediately cannot use a database..and eventually persistent (probably from a database).
If my answer helped you today, please be sure to mark the resolved button to assist others.
Christopher R Souser - Payments and Infrastructure Consultant – MSci. PA, CISSP, ITIL.