May 29, 2002 at 11:35 am
While testing a DTS package that I've created, I've noticed that once it starts a data pump task that, even if you click on the Cancel button, it continues to run. Is there a way to stop the DTS running after execution has started (short of restarting SQL Server 7)???
May 29, 2002 at 11:39 am
No. Restarting may be your only solution but you need to find the reason why this occurred.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Edited by - antares686 on 05/29/2002 11:41:51 AM
May 29, 2002 at 11:43 am
The data pump is a long running query that extracts data from an ODBC source. Is there a reason why the Cancel button won't stop the query from running?
May 30, 2002 at 6:27 am
Could be the data source is not stopping and sending back the query stopped notification. I see this occassionally with Oracle datasources. If the user canceled query doesn't come back the server will clock the connection waiting for a response.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
June 3, 2002 at 7:41 am
I'm querying against IBM's DB2 and I do believe that this is an issue with DB2 (not sending back a query stopped notification). I do know that while using QMF for Windows to query DB2, when you stop a query in QMF, it doesn't actually stop running in DB2.
June 3, 2002 at 10:03 am
That is where the problem lies. Then once you get this problem the only solution in every case I came across was to stop SQL otherwise it would just clock.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
June 3, 2002 at 6:25 pm
Assuming that when you mention the 'Cancel' button, you running the DTS package using the DTS Designer in Enterprise Manager, or you right-clicked on the package in EM and selected 'Execute,' I don't see that there is a need to stop your SQL Server. You only need to kill the Enterprise Manager process on your local machine using the Task Manager, which Ctrl-Esc will bring up. DTS packages run locally, where-ever they are called.
If you have the same problem with a DTS package that is called from an Agent job, then you should be able to right-click on the job in Enterprise Manager, and select 'Stop Job' to kill the process.
The reason why the Cancel button doesn't work is because the DTS Designer can't stop the process until it gets control back. If the task is an ActiveX script task, the cancel won't take affect until that script finishes. If its a data pump, it can cancel at the end of a batch of rows, if you're working with batches (batch size > 0), or when the pump is finished. I think anything else works like the ActiveX script. The cancel button is apparently just a notification to stop at the next opportunity. It doesn't force it. I've hit the cancel button on the last task of a package, and the package just finished normally.
As for any processes in DB2, I can't help you. I have no experience with it.
James C Loesch
Edited by - jloesch on 06/03/2002 6:34:13 PM
James C Loesch
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply