Very Computer

Hi,
I have written a triger on a base table that inserts changed and inserted
rows from the base table into a history table. It works fine when I insert
or update records from QA or directly in the base table.
But, when I create and run a DTS package that inserts rows into the base
table, the TRIGGER DOESN'T FIRE!
Please give me any suggestions how is this possible and how to prevent it.
Regards, Tanja

Tanja,

Edit the DTS task and uncheck the "Bulk Insert" check box under the Advanced folder
(I'm not 100% on the names, but I'm sure that you'll find it). Note that this will
affect performance of the import, of course.

--
Tibor Karaszi, SQL Server MVP
FAQ from Neil at: http://www.sqlserverfaq.com
Please reply to the newsgroup only, not by email.

How is the data inserted in the DTS Package.  Is it via BULK INSERT.  Because of
the limited logging of this action it will bypass triggers as does BCP and
TRUNCATE

Allan

Thanks for the respond, but is it possible to make the triger fire no matter
of the method used to insert the data. I am the owner of the table and the
trigger and I need to define the behaviour of the trigger in any case. The
other users may create and execute  DTS packages or use other methodes of
insertion. Therefore I can not control the other users and for the sake of
consistency and security I need the trigger to fire independantly of the
method used for insertion.
Please give me some further suggestions!
Regards,Tanja