A colleague of mine is experiencing a performance problem in Visual
Basic applications that he is developing to do Image/SQL updates.  He
is using Visual Basic 3.0 and the HP ODBC driver for Image/SQL.
 
The problem is that the *initial* updates to a data set or table are
very slow.  They typically take 18 to 30 seconds for a single data
set update.  Subsequent updates to that same table are much quicker,
in the range of 0.1 to 0.3 seconds.  Updates that are performed
through the ISQL utility do not demonstrate this problem.
 
In Visual Basic, he is using the 'ExecuteSQL' command to apply the
update.  When he monitors the ODBC traffic with DrDeeBee spy, he
finds that there are a huge number of calls to 'SQLFetch' and
'SQLGetData' that create an almost 1 meg log file updating one
record.
 
Can anyone explain what's going on here and suggest any way to
improve the performance of the initial updates?  Thanks for any help.
 
Software Versions:  Allbase - A.G1.05
                    Image/SQL - X.G1.00
                    ODBC Allbase.dll - A.G0.07
 
Even though Image/SQL is a "beta" version, the problem was noted with
the released version as well.
 
John Schick
Manager/Technical Support
Times Mirror Higher Education Group