Re: I need to update 30.000 rows - it must be fast.

Not necessarily. You can set your triggers to fire at the statement level (the default), or explicitly set them to fire at row level.

Your choice.

(this has nothing to do with the original OP's question, just an addition to the comment below).

jamnshelly_at_yahoo.com (james) wrote in message news:<265334b4.0203070211.40e273b2_at_posting.google.com>...
> Don't use a trigger is good advice, as the trigger will fire for each
> row updated which will slow down the original update statement.
> However, I would question the need for an alarm field at all. At some
> point you must be selecting where alarm=1. Instead of doing this why
> not
>
> select * from table_1
> where value > max
> or value < min
>
> Therefore discarding the need for any update of the alarm column.
>
Received on Thu Mar 07 2002 - 13:33:03 CST