Please explain server side cursor vs client side cursor and CacheSize=1

Please explain server side cursor vs client side cursor and CacheSize=1

Post by tome » Tue, 03 Jul 2001 17:44:46

I am using ADO to access MS-SQL server.

I understand server side cursor cause the server to copy some data about
the rows into tempdb
also i have read that client side cursor bypass the tempdb.

My question are:

1.If i am using Recrodset.CacheSize=1 what exactly happen
  to the records..?
2.Can i see the tables which created in tempdb due to query processing...?
3.Two users open server side,read only cursor with the same
   connection property and same SQL query,how many table
   will tempdb create...?

thanks in advance

tomer dror


1. client side cursor vs. server side cursor

What are the advantages/disadvantages of using each type of ADO connection/recordset
to access data in SQL 2000?

It seems that many times there are methods I'd like to use but they aren't available
using a server side cursor, but if I use a client side cursor will I have potential
problems with my code not working on some machines?  Any insight is appreciated.



2. user-defined functions

3. Client Side Cursors vs Server Side Cursors

4. SQL for "Sub Form"

5. ADO-Access2000: Server-side vs Client-side cursor

6. MDB Query on attached SQL Server Table

7. ?client-side vs server-side cursors

8. Access data pumps

9. what is a server-side cursor vs client-side

10. ?client-side vs. server-side cursors

11. Client Side and Server Side Cursors

12. ADO Cursor: Client Side or Server Side