Thanks again for the suggestion. I just created a test/sample SQL UPDATE based on a derived table and it does not seem to be that difficult. And it works fast.
>It is better to do the processing on the server if possible using a stored procedure.
>
>>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.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
