Re: Didn't ADO used to default to client-side cursors?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: jxstern (jxstern_at_nowhere.com)
Date: 12/03/04 

Date: Thu, 02 Dec 2004 17:21:53 -0800

On Thu, 2 Dec 2004 20:03:08 -0500, "David Gugick"
<davidg-nospam@imceda.com> wrote:
>Server Side Cursor
>Execute
>Fetch and load into grid
>
>Client Side Cursor
>Execute
>Auto-Fetch and create local ADO result set (ADO behind the scenes)
>Fetch and load into grid
>
>I'm not saying you need to time everything, but I would think that from
>the execution time to the user having a grid full of data would be
>faster with a server-side cursor. But as you saw, because the grid load
>is a slow process, the result set on the server remains a little longer
>and that increases the duration of the query. You could try increasing
>the packet size for the query to move more data across the network with
>each trip.

All the data moves in less than a second, but it takes almost thirty
seconds to load into the grid. The difference between the two cursor
types is a couple of tenths at most, a lot closer than I would have
guessed.

J.

Relevant Pages