Sometimes a need arises to kill a job in SQL. Currently, the only way to do this is to locate the job using the Activity Monitor and knowing what the SQL command is that you want to kill. Then kill the SQL job, and depending on what the job is, sometimes DSP will automatically restart it a few times before the failure get carried up to the job that originated it. Also, sometimes I've noticed when you kill a job - the service thread that was being utilized does not get freed back up until you restart that service. It would be nice to see the job processing and be able to kill it via DSP so you know exactly which job ties to which SQL command. Perhaps you can leverage MARKED transactions?
Unfortunately, there are too many security issues involved with allowing a user to kill a process vis DSP. I doubt we will be able to implement this as a feature.