#Oracle odbc driver configuration fetch buffer size drivers#
#Oracle odbc driver configuration fetch buffer size driver#
#Oracle odbc driver configuration fetch buffer size code#
#Oracle odbc driver configuration fetch buffer size Pc#

#Oracle odbc driver configuration fetch buffer size Pc#

It takes about 5 seconds to create 100 records! During this the PC is not so buisy. The SQLPrepare and SQLExecute by setting some parameters. I created a statement adding records in the database using I installed Oracle8.1.7 on my machine and setted up an odbc connection using it presents a list of all tables to the user, then selects all data from a table). Alternately, a description of what the app is trying to do would be helpful (i.e. If you have access to something like NuMega's TrueTime product to analyze which functions are taking too long, posting those results would be most great. If you have an application which is performant when connected to a SQL*Server database that drags when you're connected to an Oracle database, you probably have a very different set of problems.ДЇor simplicity, I'd like to suggest that you start a new thread with your question, providing all the configuration information you have.

#Oracle odbc driver configuration fetch buffer size driver#

Zhang's problems appeared to be related to his application- queries took longer via ODBC than via a direct database connection regardless of the ODBC driver used. Jeff, Were you able to find a resolution for the performance issue? We are getting ready to migrate a C++ client application/ SQL server database to a C++/Oracle server database and finding that we are experiencing the same performance issues. You might be able to use that information to contact the application's tech support to complain. You may be able to set something like Access to fetch data more logically (it may do so by default, I really don't know).Дo you know enough about ODBC to be able to follow an ODBC trace? I can probably help you identify certain ODBC functions that could be improved. Since it's easiest to fetch rows one by one, I suspect that both the app and ODBC Test are doing so. The ODBC Test utility is probably set up to make the simplest calls by default. I thought by testing with Oracle test odbc, I can eliminate the potential problem with the application. Of course, for 5 rows the speed was much quicker). But when I tested using the Oracle ODBC Test 32, the response time was comparable to that of the application, which is slow (instead of 800 rows for 40 to 100 seconds, it took 10 to 20 seconds to bring back 100 rows. I don't have the access to the application code.

#Oracle odbc driver configuration fetch buffer size code#

Alternately, there may be a configuration option in the client app that specifies how many rows are fetched at a time.Дo you have access to the code that's actually making the ODBC calls? If so, I can point you at the particular ODBC calls that are probably at fault. The app developers may not have anticipated fetching many rows from a distant database. Essentially, it's probably trying to fetch one row at a time rather than fetching many rows at a time. I suspect that the problem is that the client app which is making the ODBC calls is making them in a non-performant way. The production database is in DEC alpha machine running NT.Д«ased on all these testing, I am still not sure what might have caused the performance problem in production oracle. Response time ODBC vs SQLnet is comparable (50 msec or so) on 200 rows data retrieval. Installed Oracle to another machine in the same location on NT/wintel box. I checked the NT taskmanager, while retieving data there's no CPU consumption.Д¤. Use Oracle ODBC test instead of application - Oracle ODBC test seem to restrict the max row retrieval to 100 rows - but it still take 10 to 20 seconds, which means for 800 rows it will take the same amount of time. tried MicroSoft ODBC driver - See to be a little quicker, but still way slower than native SQLnet or Net8 ДЈ. increase prefetch count - did not seem to make a significant difference Дў. If the performance remains the same, I can say with some confidence that the app is the problem. You should be able to verify this by swapping in either the Microsoft ODBC for Oracle driver or the Merant ODBC driver for Oracle. This option essentially determines how many rows ahead we should fetch.Дo you have access to the code that's making the ODBC calls? I suspect that the root of the problem will be in inefficient calls being made to the ODBC driver.

You could try increasing the 'Prefetch Count' setting in the ODBC DSN to see if that helps matters. And 99% of the time consumed on 'data retrieval'. In SQL Worksheet, the data (800 rows) came back in 1 second, through ODBC it took 40 to 100 seconds.

#Oracle odbc driver configuration fetch buffer size drivers#

Slow performance with oracle 8.1.6 ODBC Drivers - ODBC I am trying to trouble shoot a performance problem with Oracle ODBC driver.