Kevin,

It is taking you quite a lot of time to get me the answers to the question below and the other one on the transaction as well. As promotor of SPs, I don't find your response times and the lack of solutions to my questions any convincing.

To recap the questions:

- How do you assign a null value to a column in an update SP ?

- How do you handle a multitable insert transaction (order and orderlines transaction)?

In both cases can you give me an example of code (just in concept) how you would handle that ?

Walter,


>One question though. How do you assign a NULL value to a column in an update?
>
>I'm not that fond of this approach as it could trigger all kinds of constraint and triggers on columns that essentially are not replaced. I'm not sure whether the transaction log is filled with the old and new values, but it would not surprise me.
>
>On the second question, I don't know if the transaction log gets touched if an UPDATE statement replaces the column with the same value (i.e. Set MyCol = COALESCE(@MyCol,MyCol)). Good question, I'm going to check. If it does, you could avoid it by building the UPDATE statement dynamically in the proc and then executing it using T-SQL.
>
>On the first question, if you explicitly wanted to assign a NULL, that's a good question, since the previous code is filtering out the NULLs. I'm not sure how to differentiate between an explicit NULL parameter, and a parameter that defaults to NULL because it wasn't passed. Let me check it out.
>
>Kevin