Skip to main content

Cancel specific collect background job

Answered

Comments

1 comment

  • Best answer
    Alyssa Sliney

    Hi Rolf,

    It needs to be killed on the SQL side. Killing something on the DSP side won't stop the SQL side from running but killing the SQL side should kill the job on the DSP side, as it will throw an error.

    You can run SP_Who2 or use Activity Monitor in SQL to find the SPID, the run the Kill command to stop the SQL process.

    If you have Collect configured to retry the job, it may kick off again automatically, so you may want to reset the table in Collect first as well.

    1

Please sign in to leave a comment.