I am on a new project and we are looking at having a wide table and I am wondering if anyone has done any measurement of whether it is better to have a procedure to carry out an update from the web app update the whole record or to update just the column being changed?
It's a lot easier to write the procedure to update the whole record but that will start to incorrectly skew statistics and be slower if there are lots of indexes, however writing the procedure to check which column value is different and execute the T-SQL to update just that column will be quite complex and potentially sub-optimal?
I'm a stranger in developer-land so am not aware of any standards on this ...
asked Dec 11 '12 at 11:24 AM in Default
Presume you won't be updating the PK/CI ?