>Hi,
>
>I am trying to decide on the better approach of processing/updating many rows of a table. Here is the brief description.
>
>A table of about 2000 rows has to be processed where for each row the program has to recalculate certain amounts (based on other tables) and update 2 columns. I am using Cursor Adapter as a method of getting/setting SQL Server tables. From the stand-point of efficiency of SQL Server, is it better to get all records/rows of the table, scan thorugh all rows of the cursor, update the values, and then do TableUpdate() for all rows? Or process one row at a time and call TableUpdate() after each row is processed (columns updated).
>
>TIA for any input.

RBAR - row by agonizing row is something to avoid, even in a stored procedure on the server.