he was saying that SP3 P1 was supposed to have fixed the issue, I haven't done any research on the subject, but I was just suggesting that it's possible something related to it was fixed in SP4....:)
On Fri, Dec 8, 2017 at 8:15 AM, Thomas Miskiewicz <tmisk...@gmail.com> wrote: > Does the SP4 offer some functionality in this respect or what do you mean > LJ? > > On 8. Dec 2017, at 15:58, LJ LongWing <lj.longw...@gmail.com> wrote: > > Todd, > SP4 was released earlier this week, so you might want to give that a try. > > On Fri, Dec 8, 2017 at 7:20 AM, Arner, Todd <tar...@glhec.org> wrote: > >> We have a form in Remedy that we upload user access information into on a >> bi-weekly basis. (There is about 300,000 rows) Prior to uploading the data >> to the form, we delete all of the current records and then upload the new >> data. We have been using the Application-Query-Delete-Entry in an >> escalation Run process to delete the records. This process worked fine in >> version 8.1 but has stopped working in version 9.1.3. I did find an issue >> related to the Application-Query-Delete-Entry causing a memory leak which >> causes the deletion to fail. It was supposed to have been fixed in patch 1 >> but we are still seeing the issue after installing the patch. Which brings >> me to my question, is there a better way to delete all the records other >> than using the Application-Query-Delete-Entry? As a work around for now >> we set up a job on the SQL server to truncate the data but I am not sure >> that is a good work around. I appreciate any suggestions. >> >> >> >> Thanks, >> >> Todd Arner >> >> Great Lakes >> ------------------------------ >> The information contained in this communication may be confidential, is >> intended only for the use of the recipient(s) named above, and may be >> protected under state or federal law. If the reader of this message is not >> the intended recipient, you are hereby notified that any dissemination, >> distribution, or copying of this communication, or any of its contents, is >> strictly prohibited. If you have received this communication in error, >> please forward the communication to no...@glhec.org immediately and >> destroy or delete the original message and any copy of it from your >> computer system. If you have any questions concerning this message, please >> contact the sender. >> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > >
-- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
