Re: ADO server side cursor sloooow
- From: "Bill" <no@xxxxxx>
- Date: Wed, 04 Jan 2006 22:05:57 GMT
Bill Bach wrote:
> A client side cursor will stream the data in bulk down the the
> workstation. When you need the ENTIRE data set sent across the line,
> you should use the Client-Side Cursor. Server-side cursors are much
> faster when only a small portion of the data is needed.
> Goldstar Software Inc.
> Building on Btrieve(R) for the Future(SM)
> Bill Bach
Thanks for your answer Bill. I am an experienced database developer and
I understand the basics of ADO. My problem is that if I run exactly the
same SQL statement (which selects 1,000 rows from a much larger table)
it is three times faster with a client side cursor than with a read
only forward only server side cursor.
This makes no sense because the client side cursor must dynamically
allocate memory to hold the data then load the data into that memory on
the client.
Try the same test with SQL Server and the server side cursor is faster
as I would expect. I do not understand why the server side cursor is
slower with Pervasive 9. Is there anything I can do to improve the
performance of a server side cursor?
--
..Bill.
.
- Follow-Ups:
- Re: ADO server side cursor sloooow
- From: Bill Bach
- Re: ADO server side cursor sloooow
- References:
- Re: ADO server side cursor sloooow
- From: Bill Bach
- Re: ADO server side cursor sloooow
- Prev by Date: Re: Corrupted DBP File
- Next by Date: Re: Linked Server MS SQL 2000 and Pervasive 7.82
- Previous by thread: Re: ADO server side cursor sloooow
- Next by thread: Re: ADO server side cursor sloooow
- Index(es):
Relevant Pages
|