Posted by Greg D. Moore \(Strider\) on 02/03/06 06:22

<aj70000@hotmail.com> wrote in message
news:1138930254.688661.137720@o13g2000cwo.googlegroups.com...
> hi,
>
> Here's the scenario

One thought (w/o seeing the code for the trigger) is remember, triggers fire
once per TRANSACTION not per row affected.

So it may be firing and only acting on one row.


>
> 1) I am running a DTS job to fetch some rows from Oracle
> 2) The job populates the Table A as step 1
> 3) Then it fires a update statement which updates the rows in Table B.
>
> Here's the statement
> UPDATE Table B SET
> time = case when (select median from Table A where sno = sno and Table
> A.stno=70 ) is null then time
> else (select median from Table A where Table B.sno = Table A.sno and
> Table A.sstno=70) end ,
> end
> WHERE EXISTS (select sstno from Table A where Table B.sno = Table
> A.sno)
>
> There is a trigger on table B which should fire as soon as the
> value>15.
>
> When I fire the update statement direcly with a higher value than it
> fires the trigger.
> update table B set time=17 where b.sno=1000
> But not when the job runs...
> I am puzzled.
> Thoughts?
>
> AJ
>

[Back to original message]