Oracle Provider for OLE DB in Oracle8i Release 3 (8.1.7.2.0)
Features Overview
August
2001
Product Summary
Introduced in Oracle8i Release 2, the Oracle Provider
for OLE DB gives ActiveX Data Objects (ADO) developers high performance and
efficient access to Oracle databases. Because it is a native OLE DB provider, it
offers data access optimizations and access to Oracle-specific database
features, such as support for LOBs, PL/SQL stored procedures, and REF CURSORs.
All these Oracle features and data access optimizations are generally not
available in other third-party Oracle OLE DB providers. By adhering closely to
the latest Microsoft OLE DB specification, the Oracle provider allows ADO
developers to take full advantage of OLE DB without having to sacrifice use of
Oracle database functionality. Oracle7, Oracle8, and
Oracle8i database servers can all be used in conjunction with the Oracle OLE DB
provider.The latest features in the Oracle8i Release 3 OLE DB provider
are highlighted in this paper.
Components
The Oracle Provider for OLE DB was built to improve data
access performance and reliability for ADO developers. It enhances performance
by using direct Oracle8 Call Interface (OCI) connections, rather than utilizing
ODBC as a bridge to OCI. Figure 1 demonstrates typical data access using the OLE
DB-ODBC Bridge.
Figure 2 shows data access using the Oracle provider.
By using the provider, application developers keep
the number of intermediaries data must travel through to a minimum. This allows
data to go through the most direct path possible with OLE DB.
Oracle's data access strategy has been built to handle
the high-volume, high-load of Internet application environments. The Oracle
Provider for OLE DB leverages Oracle's proven Internet infrastructure to ensure
a highly reliable, fast-performing and secure data access.
Features
The Oracle Provider
for OLE DB supports the following features:
- Scrollable and updateable rowsets
- ANSI SQL supported by Oracle and the ODBC SQL
syntax
- OS authentication, which allows Oracle to authorize
users via the operating system's security mechanisms
- Several schema rowsets
- Updateable rowsets created using joins (available
with the client cursor engine)
- Transactions support
- Local and distributed transactions which
provide explicit, commit, and abort
- Microsoft Transaction Server (MTS)-coordinated
transactions
- Autonomous transactions
- Database links support
- Unicode support
The Oracle Provider for OLE DB
also supports the following Oracle-specific features:
- PL/SQL stored procedures/functions
- Stored procedures/functions returning a rowset
- Non-Packaged stored procedures/functions
retuning rowset support
- LOBs (LONG, LONG RAW, BLOB, CLOB, NCLOB, and BFILE)
- Oracle8i Password Expiration feature
New Features in Oracle8i Release 3
New features in the latest OLE DB Provider
include:
- PL/SQL stored procedures/functions returning
multiple rowsets
- Enhanced Unicode support
- ADOX support
- Bind NCHAR parameters with SQL statements
- LOB parameters with PL/SQL stored
procedures/functions
Conclusion The Oracle Provider for OLE DB provides high performance
and reliable access to Oracle databases for ADO- or OLE DB-enabled applications.
Current ADO and OLE DB programmers should be able to easily migrate to the
Oracle provider since it complies with the latest OLE DB and ADO specifications
and allows access to Oracle-specific features.

Oracle Corporation
World
Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
+1.650.506.7000
Fax +1.650.506.7200
http://www.oracle.com/
Copyright © Oracle Corporation 2001
All Rights
Reserved
This document is provided for informational purposes
only, and the information herein is subject to change without notice. Please
report any errors herein to Oracle Corporation. Oracle Corporation does not
provide any warranties covering and specifically disclaims any liability in
connection with this document.
Oracle, Oracle8i, and PL/SQL are a trademarks of Oracle
Corporation.
All other company and product names mentioned are used
for identification purposes only and may be trademarks of their respective
owners.
|