>>>>Hey all
>>>>
>>>>Check out FAQ#33156
>>>
>>>Hi Mike,
>>>Maybe you'd want to change the explanation on "or". Unfortunately comparison in SQL doesn't work the same way in other places that we call 'shortcut'. Interestingly if it's only field3 that has changed then there would be more calls vs if all those foelds were changed.
>>
>>Hi Cetin! How are you?
>>...
>
>Hi Mike,
>Thanks I'm fine. I stand corrected,a shortcut do exist:) Those initial extra comparisons made me go wrong.

Don't forget that because of the join on the PK, only records in the incoming source table will cause firing of the OR conditions. So if there is only 1 incoming record, there will only be one real set of comparisons, plus all the setup stuff.