>Hi,
>
>I have yet another question on Cursor Adapter. Almost all my program updates are done using Cursor Adapter.
>
>I am looking at this case where one field of the SQL Server table has to be updated. The number of records is unknown but could vary from several hundred to several thousand. I have never done update of a SQL Server table where the number of records in the CA cursor is greater than about 1000. But in this case, it could be several times more (even up to 10,000). Note that only one field will be changed in the CA cursor and therefore send back for update. Does it matter?

E = mc**2
so that question should be settled ;-)

>That is, would it make a difference for the reliability of such update (time is not important, a few more seconds or even a minute is ok) when one field has been changed or more than one field?

Reliability should NEVER depend on anything other than a transaction if important.
But if I expect to have to handle millions of single column updates, I'd probably code for that case a special procedure


collecting all needed updates into a specific stream to send to a server cursor in 1 or at least only a couple of WAN calls
update remote table from that server cursor
return transaction result to client


even if you say time is not important - not blocking the server for that specific minute might become important in the future.
But I am biased by my personal definition of programming warts ;-))


>TIA