[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

RE: Best way to delete records



Hi,

 

I had worked on a requirement were we had to purge records. What we did was, take SQL logs and check all the dependent tables that gets affected.

Create a SQL job that mimics the same functionality and include it in Scheduled job. The best part of this solution was, it was powerful and silent. No ARS service downtime.

Hope this helps.

 

Thanks!

Vishal

 

From: ARSList [mailto:arslist-bounces@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, December 08, 2017 7:50 PM
To: arslist@ARSLIST.ORG
Subject: Best way to delete records

 

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 notme@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.