I have a trigger that works fine, based on records being inserted into a table. The problem is thousands of records may be added to the table at a time, and I don't want the trigger going off that many times. Just once after the records are added would be fine. Is there any way to do this?

Then trigger cannot be of any help to you, as it runs for every insert/update/delete operation based on which it is supposed to run.

May be after every such bulk inserts, you might want to invoke a stored procedure to do that job.

Hope that helps.
Cheers!

_________________________
-Vijay G
Strive for Perfection

Disable the trigger before the bulk insert, then after the records have been inserted, just run some code to do the tasks that the trigger would do.



Sal

Continue to What is Said--->
you can do as follows

ALTER TABLE trig_example DISABLE TRIGGER trig1
"Execute Insert Statments"
ALTER TABLE trig_example ENABLE TRIGGER trig1
"Execute What Trigger have to do for each of Inserted Statments"



Ahmed Ali
Software Developer

Thanks... looks like my best solution is to leave it as is since system users are adding the record via batch processes (generating purchase orders). It works, so I don't have to.

I had kind of a similar situation where before I processed the records inserted into the table with the trigger, I wanted to make sure all the relevant related data in relational tables was also there.

My solution was to create a scratch table which was populated by the insert trigger on the first table.

The scratch table had a updated flag, (default set to 0), and an insert get date() date field, and the relevant identifier from the main table.

I then created a scheduled process to loop over the scratch table and perform whatever process I wanted to perform against each record individually, and updating the 'updated flag' as each record was processed.

BUT, here is where I was a wee bit clever, in the loop over process looking for records in the scratch table that had a 'update flag = 0', I also added the AND clause of 'AND datediff(mi, Updated_Date, getdate())> 5'. So the record would not actually be processed until 5 minutes AFTER it was inserted into the scratch table.