|
 |
activex_data_objects thread: adUseClient and adUseServer CursorLocations
Message #1 by keith.moore@s... on Mon, 2 Dec 2002 04:45:53
|
|
Hi,
is there any difference between using adUseClient and adUseServer when
connecting to an SQL Server 7 database using the native OLE DB provider.
I currently use server-side cursors and was thinking about using client
side cursors.
I realize there may be a performance change but other than that would I
need to change code?
Are there certain things you can/can't do when using client side cursors?
Thanks.
Message #2 by "Phil Griffiths" <pgtips@m...> on Mon, 2 Dec 2002 09:32:57
|
|
Keith,
Certainly there is a difference, mainly in the way they are implemented.
If you use adUseClient then ADO implements the cursor. If you use
adUseServer (the default) then SQL Server implements the cursor (although
internally it may not actually use a cursor at all). I think the main
practical difference is that server-side cursors cannot return multiple
recordsets.
There's some good reading in MSDN. Try this URL (and also expand the tree
in the left frame to see other details):
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/adosql/adoprg02_30tv.asp
rgds
Phil
>-------------------------------------------------------
> Hi,
> is there any difference between using adUseClient and adUseServer when
> connecting to an SQL Server 7 database using the native OLE DB provider.
> I currently use server-side cursors and was thinking about using client
> side cursors.
> I realize there may be a performance change but other than that would I
> need to change code?
> Are there certain things you can/can't do when using client side cursors?
> Thanks.
|
|
 |