A user accidentally bulk added CSIs to a bunch of records that should not have them.
What is the safest way to bulk remove CSIs? Can I just delete the rows from T_CUST_ACTIVITY in SSMS?
They don't have any actions.
Are there any other tables connected to CSIs that I would need to worry about?
Thanks,
Shelly Binkley
Shelly Binkley (she/her) said:Can I just delete the rows from T_CUST_ACTIVITY in SSMS?
I've been deleting unwanted CSIs exactly that way, via a scheduled SQL Agent job, since 2013, with no ill effects.
I've also done this on occasion.
A lot of my TNEW Stored Procedures create CSIs and we also had a lot of junk legacy CSIs that we needed clearing out from automated surveys that were blank.
I do a double check with
use impresario SELECT top 10 * FROM T_CUST_ACTIVITY a LEFT INNER JOIN T_ISSUE_ACTION b ON a.activity_no = b.activity_no ORDER BY a.activity_no DESC
Just to be super careful to not leave divorced lines in the action steps: I been known to catching the deleted activity_no from the DELETE action in T_CUST_ACTIVITY and running a follow up DELETE in T_ISSUE_ACTION with those activity_no as a WHERE. When I'm happy with what I've set up I commit the transaction.
Hi all,We are looking at deleting some of our old CSIs which are no longer needed. We also want to establish a process for the regular deleting of some CSIs once they are no longer needed.Appreciate it may be pretty simple but would anyone be happy to share the code the used for this so we can have a look at it before doing some testing?Some of ours might have actions, but otherwise are pretty straight forward. Thanks, Donald