Steve, an interesting article.

I generally follow a similar pattern to yours.

One thing I notice you haven't mentioned is labelling. I view this as key to successfully managing a...

alexd1980, you probably have ansi nulls turned on.

In this case NULL=NULL always evaluates to unknown, so your if expression evaluates the ELSE branch.

This is why it doesn't matter...

my fault for adding to the confusion - didn't spot you were copying rows across to your other table

don't have any bright ideas for the timestamp...

I think simplest to use some dynamic sql here - use exec (@sql) where @sql represents a built string from your input params.

eg,

set @sql = 'Select col1, col2,..

FROM...

you should update the table that the trigger is on, referencing the inserted table & joining over the primary key.

that way you influence the value of the row(s) being...

not that I know much about this, but I suspect its something to with a transaction wrapped around your sp (possibly implicit).

If you check your sp interactively you should...

Anyone interested in digging further should check out BOL.

Its simplest to look for 'NULL Comparison Search Conditions' in the index & follow the link to 'Null Values' at the...

I realised the topic specifically covered variables, but some of these aspects also apply more widely to any expression involving null.

Under sql92 any expression involving null directly evaluates to...