There may be occasions when it is necessary or helpful to stop a Collect task; when, for example, the table becomes too large and the user does not want to finish building it. There also may be occasions when it is useful to stop a job running in Admin.
Stopping a Collect Extract
Collect automation allows users to build and execute a variety of data extraction packages. Collect notifies the user when the package has completed, updating some metrics as well. Collect does not, however, allow users to abort those package executions once they have been started. Execution can be aborted indirectly, as per the following methods.
WARNING: When you use one of these methods to abort a Collect package execution, Collect will receive an error message and update the extract with a failed status. Collect’s automatic recycling feature defaults to 3, so it will restart the execution automatically 3 times. In order to avoid manually aborting package execution 4 times (each time waiting to see if another appears), you can disable the recycling feature by navigating to Common > Configuration > Modules > Parameters - Collect and setting the Recycle Job Max value to 0 (General Settings tab). You can restore the setting to its prior value after aborting the package execution. See https://dsphelp.syniti.com/706/general/Common/Page_Desc/Parameters_Collect.htm for details.
Below is a list of package types and the methods used to stop package execution.
Locate the process SPID in SQL Server Activity Monitor and end it.
Locate the DTExec.exe process in the Windows Task Manager on the DSP app server and end it.
NOTE: Take care using this method when multiple SSIS packages are running simultaneously. Since DTExec.exe processes do not specify associated packages, you can inadvertently end a process you intend to keep running.
Locate the batch job in the Data Services Management Console and end it.
Syniti Data Replication
Locate the replication in Syniti Data Replication Management Center and stop it.
Stopping a Job on the DSP Platform
You can stop a job by identifying the JobID value and updating the record's Status to Failed in the CranSoft.dbo.JobQueue table. The currently running task, however, will continue to run. You can stop the currently running task by ending the SQL Server SPID or Windows process that it executed.
NOTE: Some webapps will attempt to start a similar job once the Job Status is set to Failed. This behavior must be addressed on a case by case basis.