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

Timeout on SQL calls when using the Oracle Provider for OLEDB

P: n/a
We are using ADO with the Otacle Provider for OLEDB in our COM+ MTS
C++ client (Oracle 8.1.
It seems there is no way to timeout our ORACLE SQL calls, in case the
database is verry slow for what-ever reason. Our calls just wait for
the SQL to complete and we do not seem to have any control over the
time it takes. The normal way to achive this in ADO is by setting the
ConnectionTimeout and CommandTimeout properties of the ADO's
connection and command objects. However, we understand this is not
supported by the Oracle Provider for OLEDB, so it's not an option.

Can anyone suggest a workaround. It seems like a major issue to me.

One option I can think of is using the MTS transaction timeout
setting, but firstly this does not seem to work well with Oracle
either, and also, we do not want to run all SQL calls in a
transaction, as there is an overhead attached to this, when
transaction is not needed otherwise.
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.