By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,321 Members | 1,190 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,321 IT Pros & Developers. It's quick & easy.

Performance probs with Connect 4.2 for Oracle Wire

P: n/a


We've just started evaluating the Data Direct ODBC Oracle driver and
comparing performance with Oracle's own driver in a development project
we're undertaking.

We have struck a problem - functionally the driver's working OK, but we
have a performance problem that is associated with the ODBC
connectivity layer.

In our application, we use stored procedures a lot, and return result
sets from them.

It seems that in the Wire driver, every time a statement is executed
that calls a stored procedure, the column metadata is returned even when
it's not explicitly asked for with the SQLDescribeCol calls. If we
select the driver option to "Describe at prepare time" and do the
statement as a prepared statement, this doesn't make any difference.
(However, for a 'normal' query, i.e. not a stored proc, this works as
We understand that the metadata could well be different from one call to
the next of a stored procedure, which is why it can't really be worked
out at prepare time, however this is clogging up the LAN. It should only
come back to the app from the server if it is explicitly asked for?

The amount of metadata is frequently a number of times larger than the
data itself.

Because we are also executing queries quite frequently, (with small
result sets), this is causing overall performance degradation.

Any ideas or recommendations?


Posted via
Jul 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.