![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
SQL / AS is great - but one thing annoys me - if I want to cancel a dts task it seems as if it never works...it persists on doing a package till the end and before starting a new package it will cancel and sometimes it just doesn't get back when cancelled. Is there someway to make this better - a parameter or something ? \Michael Vardinghus |
#3
| |||
| |||
|
|
In message <#fx1VJeWEHA.3988 (AT) tk2msftngp13 (DOT) phx.gbl>, Michael Vardinghus michaelvardinghus (AT) notexisting (DOT) com> writes SQL / AS is great - but one thing annoys me - if I want to cancel a dts task it seems as if it never works...it persists on doing a package till the end and before starting a new package it will cancel and sometimes it just doesn't get back when cancelled. Is there someway to make this better - a parameter or something ? \Michael Vardinghus There are no extra magic switches you can use, and to be honest I don't think this would be a good idea. What you are asking for is a power button really. If you can safely cancel and operation then a well written task will implement the event handlers and check the cancel flag as often as appropriate. In QA, you don't expect a long running query to be cancelled immediately, since it will often have to perform a rollback to ensure the data is left in a consistent state. Not all tasks can support transactions or would you want them to, so in these cases, there is no other option to let things complete. -- Darren Green (SQL Server MVP) DTS - http://www.sqldts.com PASS - the definitive, global community for SQL Server professionals http://www.sqlpass.org |
![]() |
| Thread Tools | |
| Display Modes | |
| |