client side cursor vs server side cursor regarding memory used

I have a VB 6 app that imports data from a text data source via JET 4.0 to a
SQL server database.

Although I did not receive the error myself but when my client tested it,
they received a out of memory error. There are about 60K+ rows with 150
columns each of text and numeric values. Obviously, there are checks that
need to be done like, the client system config, etc. I wanted to know
whether using a different type of cursor made any difference in the usage of
memory. I may have some misconceptions regarding client side cursors and
would like to dispel some of it if false. For example, I think that since
the client side cursor keeps track of the cursor on the client side, it'd
retain all the records retrieved so far whereas the server side cursor might
not. Maybe I am confusing it with disconnected recordsets.

Any insights provided in this matter will be greatly appreciated.
Thanks

Jiho


.

Relevant Pages

  • Re: ... after Opening a record set
    ... I will point out that as long as one can live with a client cursor (all records retrieved to the client machine during the ... it is better to loop based on EOF unless there is a compelling reason to do otherwise. ... >> It is not a reliable method of retrieving records from a recordset. ...
    (microsoft.public.vb.database.ado)
  • Re: ORATCL help needed!
    ... set cursor ... Wow, An Oratcl 3.3. ... It is coded with the the OCI layer released with Oracle ... Oracle instant client is available for many many platforms, ...
    (comp.lang.tcl)
  • Re: cancel ADO2.8 asynchron queries over WAN, takes long time
    ... >> the .open method first creates the recordset at the server. ... I use clientside cursor to minimalize the traffic... ... You do not want to be managing any types of cursors on the client ... > doing so over a slow link is a bad choice. ...
    (microsoft.public.data.ado)
  • Re: cancel ADO2.8 asynchron queries over WAN, takes long time
    ... >> the .open method first creates the recordset at the server. ... I use clientside cursor to minimalize the traffic... ... You do not want to be managing any types of cursors on the client ... > doing so over a slow link is a bad choice. ...
    (microsoft.public.sqlserver.programming)
  • Re: VB connection to SQL server
    ... > the client machine begins to lose its relevance and accuracy as soon as it ... > aware that the data is probably out of date, a client sided cursor might ... > design minimises the possibility that records will have changed in the ... >> The Database server is in the office, and people use the Vb program from ...
    (microsoft.public.vb.database)