VB Forum / Database Access / August 2007

Depending on the other options you choose, a "server" cursor is created and
maintained on the remote server (if there is one). This approach permits you
to see data as it's changed by other applications. Supposed you select the
seats on an airline flight and create a server-side cursor to manage the
rowset. As you navigate from row to row the current value of the row is sent
to the client.

With a client-side (or "detached") cursor, the client gets a "snapshot" of
the rows so if changes are made on the server you don't see them--nor do
others see your changes. To see current data on one or a set of rows you
have to re-execute the query.

Incidentally, ADO.NET no longer supports server-side cursors. I show how
they can be implemented using ANSI CURSORs in my books.