Re: Access 7.0 -> Informix 7.1-2

A followup just for the record. There was something wrong with the server when I ran the indicated tests on MS Access and ODBC connection. I found out shortly afterward as I did think the timings where incredibly long. When the server was again runing as it should both MS Access via OpenLink ODBC drivers and Informix dbaccess running on the server where the database is installed, take on the order of 2 seconds to open the table of 1632 rows and read all rows (it's hard to time at this speed). Testing a selection on an index returning about 31.000 rows from a table of about 1.000.000 rows, dbaccess used about 33 seconds to select them all and write them to a file. With MS Access I saw the last row of the query after about 16 seconds. (MS Access have then read all the 31.000 rows from the database and stored them locally on my PC.) The interesting part here is that I get the same or better performance using MS Access via ODBC as I see using dbaccess on the server on similar operations. I repeat again that these are *very* informal tests Nils.Myklebust@idg.no (Nils Myklebust) wrote: :sabba <sabba@inrete.it> wrote: : ::Donald Mac Phee Ii wrote: ::> .... ::I just warn u .. i'm having big performance problems using informix cli ::7.2 plus intersolve odbc to access informix 7.0 in the access ::environment. : :I take it that you mean MS Access? : ::it takes about 2 minutes to open a table (18 fields ... about 185 bytes ::each record .. and fetching 226 records) on a wnt4 box running access7 :: ::could it be you know why ? :May be you can tune the fetch buffer size (FETBUF_SIZE ??) :environement variable in I-Net on your PC and in the sqlhosts file on :the server and see better performance. :: ::or is it just that intersolve drivers sucks ?! :) :Not too unlikely, but I haven't tested these newer versions. (This was :*realy* true some time (a year or two) ago.) : :With OpenLink (the Enterprise (server based) version) it takes less :than 10 seconds to open a table and another 20 to 30 seconds to see :the last row out of 1632 (27 columns, 265 bytes pr. row) :This is still slow, but a major part of that is MS Access whose ODBC :interface isn't exactly known to be fast. Using VB with RDO or other :means of more direct access to ODBC, gives much faster results. :Also this is with no tuning or anything done to the ODBC drivers, :simply a straight install. : :Interestingly trying a similar operation using dbaccess on the Unix :machine (where the database is installed) took more than a minute. :I did: : select * from tablename :Selected Output, New file, gave a filename and timed it from I hit :return to the operation finished. :Why this would be so much slower I don't know. :Accessing the first row with the above select statement is much faster :(almost instantaneous) using dbaccess on the same machine and table. :Such an access is however also very fast with the OpenLink drivers :using other tools than MS Access. : :NB! The above tests where done while other users where active. It's :not a proper test that should be compared to *anything* you see in any :other environement without full consideration of the limits. You :*have* to test for your self. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org