🚀 go-pugleaf

So, changing the cursor between client and server makes
very obvious difference  in speed?

And , the quickest method is using stored procedure ?


"Vassiliev V.V." <vv_vas@iname.com> wrote :3c36e962_1@dnews...
> You are wrong, at least what concerning MS Access and ADO (or Client
Cursor
> Engine in OLEDB). MS Access does not support batch updates, they could be
> done only on ClientCursor. I will citate "Optimistic Remote Updating in
the
> Client Cursor Engine" article from "Microsoft Data Access Technical
> Articles" help file:
>
> "In optimistic remote updating, the key to the complexity is that the CCE
> does not "own" the data it is ultimately updating. Instead, the data is
> owned by some specific provider, and the CCE must submit update requests
in
> the form of SQL commands. (This is also sometimes referred to as
query-based
> updating, or QBU.) "
>
> So, data are not updated directly, but by executing SQL commands. Parsing
> SQL command takes much more time then just updating data and batch
updatings
> on ClientCursor could be 100-1000 times slower then inserting rows on
server
> cursor.
>