RE: C++ client SDK

Thank you your answer, but I have still some open questions in my mind. In the ESQL header called sqlhdr.h the "FetBufSize" global variable is defined. But in the case of using C++ interface the included header is the it.h where is no anything defined like in ESQL. Am I right to say that the only way is to set this buffer is by the setting environment variable? I'd like to ask that what will happen if the default (4k) buffer size is not enough to fetch the entire row, because its size is bigger. Is this buffer at the client side after the TCP socket part? Thank you, Andor Rozsnyai -----Original Message----- From: Art S. Kagel [mailto:kagel@bloomberg.net] Sent: Tuesday, December 05, 2000 12:14 AM To: Rozsnyai, Andor (MED) Subject: Re: C++ client SDK The global variable that controls the transfer buffer size is FetBufSize range is 4096 <= FetBufSize <= 32767 There is also an environment variable that has the same effect: FET_BUF_SIZE Art S. Kagel "Rozsnyai, Andor (MED)" wrote: > > Hi, > > I've a strange performance issue with Cursors in case of extra wide tables > (huge amount of fields). > To read rows by a read-only cursor takes: > > ~50 columns with table -> 50-60ms > ~130 column with tables -> 480-500ms > > I read some settings in the documentation of ESQL to resize the fetch buffer > of cursor, but I don't know what can I do in C++ interface. > > Does anyone help me? > > Thank you in advance, > > Andor Rozsnyai