Timeout on SQL calls when using the Oracle Provider for OLEDB

From: Tzanko <tzanko.tzanev_at_strategicthought.com>
Date: 2 Jun 2004 06:46:24 -0700
Message-ID: <88cb94d1.0406020546.85ad741_at_posting.google.com>



Hi,
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. Received on Wed Jun 02 2004 - 15:46:24 CEST

Original text of this message