hmmm. I think the question asked is:)Is there a difference in performance between UPDATE 1 column in 1 row of a table compared to UPDATE all columns in 1 row of a table.I thought that there would be but I'm not so sure...Following code makes up some sample data (random strings) and then updates half of them. The first UPDATE does only one column, the second updates all the columns (and transposes two of them).On a dataset of 45190 rows the IO stats / execution plans / and time in batch are exactly the same for the two UPDATESIF OBJECT_ID('tempDB..#foo') IS NOT NULL DROP TABLE #fooCREATE TABLE #foo ( [Id] INT IDENTITY (1,1) , [valA] NVARCHAR(32) , [valB] NVARCHAR(32) , [valC] NVARCHAR(32) , [valD] NVARCHAR(32) , [valE] NVARCHAR(32) )-- Sample Data for #foo (random data)INSERT #foo ( [valA] , [valB] , [valC] , [valD] , [valE] )SELECT CAST(CAST(NEWID() AS VARBINARY(32)) AS VARCHAR(32)) , CAST(CAST(NEWID() AS VARBINARY(32)) AS VARCHAR(32)) , CAST(CAST(NEWID() AS VARBINARY(32)) AS VARCHAR(32)) , CAST(CAST(NEWID() AS VARBINARY(32)) AS VARCHAR(32)) , CAST(CAST(NEWID() AS VARBINARY(32)) AS VARCHAR(32))FROM information_schema.columns a CROSS JOIN ( SELECT 0 AS [seed] UNION SELECT 1 UNION SELECT 2 UNION SELECT 3 UNION SELECT 4 UNION SELECT 5 UNION SELECT 6 UNION SELECT 7 UNION SELECT 8 UNION SELECT 9 ) b-- Objects in #fooSELECT COUNT([Id]) FROM #foo-- Test SuitesSET STATISTICS IO ON UPDATE #foo SET [valA] = 'FOOO' WHERE [Id] % 2 = 1 UPDATE #foo SET [valA] = 'FOOO' , [valB] = 'BAR' , [valC] = 'WOO' , [valD] = [valE] , [valE] = [valD] WHERE [Id] % 2 = 1Any thoughts?Charlie===============================================================Msg 3903, Level 16, State 1, Line 1736The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION