DTS package step to disable

Hi DBA's,

I have a DTS package that has steps 1 to 13. Say for a given situation I do not want the package to execute Step 11, 12 and 13 but steps 1 to 10 should be executed and the package should be treated as a sucess. Please confirm if the following approach is correct.

1. I go to Local Packages on the EM and then open up my package in designer view.
2. I go to step 11, right-click to go to WorkFlow properties. I go to Options tab and under execution I select disable this step.
3. I repeat the process for step 12 and step 13. Now 11 to 13 are disabled. I now execute the package.

Is the above correct?That will work in your description - but that is very hardwired - when would you not execute those steps ?|||Originally posted by rnealejr
That will work in your description - but that is very hardwired - when would you not execute those steps ?

Well step 11 is a stored proc which is failing now in the DTS package. So I want to disable step 11 and all the further steps. I intend to run step 11 in the QA. I tried to automate it by includusing step 11 in a DTS package. I am concerned with only step 1 to step 10. the rest of the steps 11-13 can be done manually.

DTS import: Disabling trigger and Constrains before import ?

Hi,
Is it a good idea to disable trigger and contrains in the source Database
before using DTS import
and enable trigger and contrains in the destination database after the
import has been completed ?
Thank you
DannyDanny,
Disabling triggers and constraints is not a good idea unless you know your
data and load process well enough to be sure that you will not be subverting
the reasons that the triggers and constraints were created.
But, if you know your import logic is good, then "Yes" you will receive some
load benefits by dropping or disabling the triggers and constraints in the
_target_ database until the load is complete, then reenable (or recreate)
them. (There is no point in disabling these in the source database.) You
could ask the same question about indexes, dropping them before the load and
recreating afterward.
The other factor is the amount of data being imported. If you are bringing
in a fraction of a percent in a daily update, then you may not want to do
any of this. If you are totally rebuilding the contents of the database,
then simplifying what the load must do is a good thing.
Your mileage may vary.
Russell Fields
"Danny Presse" <DannyP@.congresmtl-NO-SPAM.com> wrote in message
news:u9#OZDz6DHA.632@.TK2MSFTNGP12.phx.gbl...

quote:

---

> Hi,
> Is it a good idea to disable trigger and contrains in the source Database
> before using DTS import
> and enable trigger and contrains in the destination database after the
> import has been completed ?
> Thank you
> Danny
>

---

DTS import: Disabling trigger and Constrains before import ?

Hi,
Is it a good idea to disable trigger and contrains in the source Database
before using DTS import
and enable trigger and contrains in the destination database after the
import has been completed ?
Thank you
DannyDanny,
Disabling triggers and constraints is not a good idea unless you know your
data and load process well enough to be sure that you will not be subverting
the reasons that the triggers and constraints were created.
But, if you know your import logic is good, then "Yes" you will receive some
load benefits by dropping or disabling the triggers and constraints in the
_target_ database until the load is complete, then reenable (or recreate)
them. (There is no point in disabling these in the source database.) You
could ask the same question about indexes, dropping them before the load and
recreating afterward.
The other factor is the amount of data being imported. If you are bringing
in a fraction of a percent in a daily update, then you may not want to do
any of this. If you are totally rebuilding the contents of the database,
then simplifying what the load must do is a good thing.
Your mileage may vary.
Russell Fields
"Danny Presse" <DannyP@.congresmtl-NO-SPAM.com> wrote in message
news:u9#OZDz6DHA.632@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Is it a good idea to disable trigger and contrains in the source Database
> before using DTS import
> and enable trigger and contrains in the destination database after the
> import has been completed ?
> Thank you
> Danny
>