ckUseClient

An ADO.Net provider factory will use a default client side cursor. A client-side cursor offers more flexibility. All data is retrieved to the local machine and then operated on there, allowing operations not normally supported by servers like sorting and resorting the data and additional filtering. SQL statements are executed at the server, so for statements that restrict the result set with a WHERE clause, only the reduced result set is retrieved to a local cursor.

ckUseInMemory

An ADO.Net provider factory will use an in-memory dataset cursor. An in-memory dataset cursor does not load data from the database. Data are added, edited and removed from the in-memory dataset structure. Optionally, you can fill dataset cursor with data from the database and update the database with data from dataset cursor using DbDataAdapter.

ckUseServer

An ADO.Net provider factory will use a forward only server side cursor. A server-side cursor offers less flexibility, but may be more advantageous (or necessary) for large result sets. Using a server-side cursor becomes necessary when the sheer size of a result set exceeds the available disk space that would be needed to create the client-side cursor. Also, many servers only support unidirectional cursors. Moving the record pointer in the dataset backward (even one record) through the result set is not allowed with this cursor.