The information in this article applies to:
SYMPTOMSWhen you call an Oracle stored procedure through Remote Data Objects (RDO) or through ActiveX Data Objects (ADO) using Command.Refresh, the Microsoft Oracle ODBC Driver version 2.0 is slower than version 1.0. CAUSEThe underlying ODBC API call (SQLProcedureColumns) was changed in version 2.0 of the MS Oracle ODBC Driver to accommodate Oracle package support. By making this change, the SQL for the API call increased ten-fold. The larger SQL statement results in the slower execution of Oracle stored procedures. RESOLUTIONWhen using RDO there is no workaround. SQLProcedureColumns is always called. With ADO, if all of the Command attributes are set, the parameters collection is defined and Command.Refresh is not used, then SQLProcedureColumns is not called. For an example of how to use ADO so that SQLProcedureColumns is not called, please see the following article in the Microsoft Knowledge Base: Q176936 INFO: Visual Basic Accessing an Oracle Database Using ADO STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONFollowing is the SQL statement that SQLProcedureColumns creates on Oracle (captured through Oracle SQL trace):
If you use ADO (as demonstrated in KB article Q176936) instead of RDO, the
above statement is never issued to Oracle. Because of this, ADO can execute
an Oracle stored procedure much faster than RDO.
© Microsoft Corporation 1998, All Rights Reserved. Additional query words: MS Oracle ODBC Driver rdo ado stored procedure kbVBp500 kbRDO kbOracle kbODBC kbDriver kbDatabase kbVBb kbADO
Keywords : |
Last Reviewed: August 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |