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
>