different types of cursors

Question

different types of cursors

psconsulting

SSC Eights!

Points: 944
More actions
August 27, 2002 at 12:59 pm

#158088

I was just reading an article regarding cursor performance. They mentioned two different types of cursors. One on the client side cursor and the other a server side cursor. How can you force SQL to handle it either which way or maybe I have misunderstood something?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

katravax Old Hand Points: 353 More actions · Answer 1

It's not set on SQL Server per se, it's set in the client library you use to access SQL Server. ADO, for example, has settings for specifying whether it should use server- or client-side cursors.

- Troy King

psconsulting SSC Eights! Points: 944 More actions · Answer 2

Thanks for the post! So if I am understanding you correctly, this pertains more to designing an application rather than to me running a cursor from QA massaging data?

psconsulting SSC Eights! Points: 944 More actions · Answer 3

Thanks for the post! So if I am understanding you correctly, this pertains more to designing an application rather than to me running a cursor from QA massaging data?

Antares686 SSC Guru Points: 125444 More actions · Answer 4

Correct. When talking about Client Side and Server Side cursors yes, it is based on the application design and the underlying client library used to create the connection (OLE, ODBC, other) that support this option.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

crosspatch Hall of Fame Points: 3168 More actions · Answer 5

You may well find in programming circles a client side cursor reffered to as a 'disconnected recordset'. One of the great advantages of client side for things like web apps is that you only need to maintain the database connection for the time needed to generate the cursor. So as soon as the cursor is completed it is passed to the client and you can break the db connection. The client knows nothing and can browse the data as normal.

Couple of other points about Cursor performance, avoid using any form of updateable Cursor (locks and db connection etc.) and also try to use forward only cursors again less consumption of resources

I have found it is possible to please all of the people all of the time if you do exactly what they want. Harold Macmillan 1961

crosspatch Hall of Fame Points: 3168 More actions · Answer 6

You may well find in programming circles a client side cursor reffered to as a 'disconnected recordset'. One of the great advantages of client side for things like web apps is that you only need to maintain the database connection for the time needed to generate the cursor. So as soon as the cursor is completed it is passed to the client and you can break the db connection. The client knows nothing and can browse the data as normal.

Couple of other points about Cursor performance, avoid using any form of updateable Cursor (locks and db connection etc.) and also try to use forward only cursors again less consumption of resources

I have found it is possible to please all of the people all of the time if you do exactly what they want. Harold Macmillan 1961