Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
One row at a time vs. all rows
Message
From
27/10/2010 10:46:55
James Blackburn
Qualty Design Systems, Inc.
Kuna, Idaho, United States
 
General information
Forum:
Microsoft SQL Server
Category:
Other
Environment versions
SQL Server:
SQL Server 2005
Miscellaneous
Thread ID:
01487153
Message ID:
01487159
Views:
53
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.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform