Is that a point, or a statement of fact? It is a fact that you do pass all the parameters back - regardless of whether the values changed or not. One point might be that scenario is not good. Another point might be that it does not matter.

My POV is with the latter. Sure, you could place code - either at the client or the server - that checks to see which fields have changed. Or, you could be efficient about it - using the ADO Command Object - and populate the parameters and execute the procedure. So what if you are writing the same values back. If I bypassed the overhead of comparing values - what is the big deal? I say this in light of real world experience - with 700 + users hitting a server at the same time - updating records all day. The time to update a record is as fast as a blink of an eye.

I would ask the question of whether this is a "real" problem or a "perceived" problem...

< JVP >

>
John's point is that the client has to pass in the entire list of parameters even if there is only a single field to be updated.
<