1. Oracle 12c Oledb Provider Download
2. Oracle 11g Download 64 Bit
3. Oracle Provider Download Speeds
4. Oracle Jce Provider Download
5. Oracle Provider For Ole Db Download

Re:Oracle 7.3.3 or 7.3.4 download 116853 Sep 6, 2002 5:17 AM ( in response to 295084 ) call oracle support ask them for cd pack. MSDAORA is no longer supported by current versions of Oracle. It was last updated for Oracle 9, and is no longer being updated. For 64 bit, we need to download and use the Oracle client and the provider from their site for connecting with SQL. Oracle has a 64-bit version that is usable for us. Oracle is a provider which is supported by Oracle. Oracle Data Provider for.NET. Oracle Data Provider for.NET (ODP.NET) features optimized ADO.NET data access to the Oracle database. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, self-tuning statement cache, and fast connection failover. MSDASQL is an OLEDB provider that connects to ODBC, instead of a database. MSDASQL ships with the Windows operating system, and Windows Server 2008 & Windows Vista SP1 are the first Windows releases to include a 64-bit version of the technology. The Microsoft OLE DB Provider for Oracle allows ADO to access Oracle databases. Connection String Parameters. To connect to this provider, set the Provider argument of the ConnectionString property to: MSDAORA Reading the Provider property will return this string as well.

-->

A .NET Framework data provider is used for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, placed in a DataSet in order to be exposed to the user as needed, combined with data from multiple sources, or remoted between tiers. .NET Framework data providers are lightweight, creating a minimal layer between the data source and code, increasing performance without sacrificing functionality.

1. Oracle Data Provider for.NET. Oracle Data Provider for.NET (ODP.NET) features optimized ADO.NET data access to the Oracle database. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, self-tuning statement cache, and fast connection failover.
2. Download OraOLEDB90101.exe and run it. The full instructions are Instructions for Installing Oracle Provider for OLE DB. If you do some searching on MSDN they say that BLOB data is not supported with the Microsoft data provider, MSDAORA.1.

The following table lists the data providers that are included in the .NET Framework.

.NET Framework data provider	Description
.NET Framework Data Provider for SQL Server	Provides data access for Microsoft SQL Server. Uses the System.Data.SqlClient namespace.
.NET Framework Data Provider for OLE DB	For data sources exposed by using OLE DB. Uses the System.Data.OleDb namespace.
.NET Framework Data Provider for ODBC	For data sources exposed by using ODBC. Uses the System.Data.Odbc namespace.
.NET Framework Data Provider for Oracle	For Oracle data sources. The .NET Framework Data Provider for Oracle supports Oracle client software version 8.1.7 and later, and uses the System.Data.OracleClient namespace.
EntityClient Provider	Provides data access for Entity Data Model (EDM) applications. Uses the System.Data.EntityClient namespace.
.NET Framework Data Provider for SQL Server Compact 4.0.	Provides data access for Microsoft SQL Server Compact 4.0. Uses the System.Data.SqlServerCe namespace.

Core Objects of .NET Framework Data Providers

The following table outlines the four core objects that make up a .NET Framework data provider.

Object	Description
Connection	Establishes a connection to a specific data source. The base class for all Connection objects is the DbConnection class.
Command	Executes a command against a data source. Exposes Parameters and can execute in the scope of a Transaction from a Connection. The base class for all Command objects is the DbCommand class.
DataReader	Reads a forward-only, read-only stream of data from a data source. The base class for all DataReader objects is the DbDataReader class.
DataAdapter	Populates a DataSet and resolves updates with the data source. The base class for all DataAdapter objects is the DbDataAdapter class.

In addition to the core classes listed in the table earlier in this document, a .NET Framework data provider also contains the classes listed in the following table.

Object	Description
Transaction	Enlists commands in transactions at the data source. The base class for all Transaction objects is the DbTransaction class. ADO.NET also provides support for transactions using classes in the System.Transactions namespace.
CommandBuilder	A helper object that automatically generates command properties of a DataAdapter or derives parameter information from a stored procedure and populates the Parameters collection of a Command object. The base class for all CommandBuilder objects is the DbCommandBuilder class.
ConnectionStringBuilder	A helper object that provides a simple way to create and manage the contents of connection strings used by the Connection objects. The base class for all ConnectionStringBuilder objects is the DbConnectionStringBuilder class.
Parameter	Defines input, output, and return value parameters for commands and stored procedures. The base class for all Parameter objects is the DbParameter class.
Exception	Returned when an error is encountered at the data source. For an error encountered at the client, .NET Framework data providers throw a .NET Framework exception. The base class for all Exception objects is the DbException class.
Error	Exposes the information from a warning or error returned by a data source.
ClientPermission	Provided for .NET Framework data provider code access security attributes. The base class for all ClientPermission objects is the DBDataPermission class.

.NET Framework Data Provider for SQL Server (SqlClient)

The .NET Framework Data Provider for SQL Server (SqlClient) uses its own protocol to communicate with SQL Server. It is lightweight and performs well because it is optimized to access a SQL Server directly without adding an OLE DB or Open Database Connectivity (ODBC) layer. The following illustration contrasts the .NET Framework Data Provider for SQL Server with the .NET Framework Data Provider for OLE DB. The .NET Framework Data Provider for OLE DB communicates to an OLE DB data source through both the OLE DB Service component, which provides connection pooling and transaction services, and the OLE DB provider for the data source.

Note

The .NET Framework Data Provider for ODBC has a similar architecture to the .NET Framework Data Provider for OLE DB; for example, it calls into an ODBC Service Component.

Comparison of the .NET Framework Data Provider for SQL Server and the .NET Framework Data Provider for OLE DB

The .NET Framework Data Provider for SQL Server classes are located in the System.Data.SqlClient namespace.

The .NET Framework Data Provider for SQL Server supports both local and distributed transactions. For distributed transactions, the .NET Framework Data Provider for SQL Server, by default, automatically enlists in a transaction and obtains transaction details from Windows Component Services or System.Transactions. For more information, see Transactions and Concurrency.

The following code example shows how to include the System.Data.SqlClient namespace in your applications.

.NET Framework Data Provider for OLE DB

The .NET Framework Data Provider for OLE DB (OleDb) uses native OLE DB through COM interop to enable data access. The .NET Framework Data Provider for OLE DB supports both local and distributed transactions. For distributed transactions, the .NET Framework Data Provider for OLE DB, by default, automatically enlists in a transaction and obtains transaction details from Windows Component Services. For more information, see Transactions and Concurrency.

The following table shows the providers that have been tested with ADO.NET.

Driver	Provider
SQLOLEDB	Microsoft OLE DB provider for SQL Server
MSDAORA	Microsoft OLE DB provider for Oracle
Microsoft.Jet.OLEDB.4.0	OLE DB provider for Microsoft Jet

Note

Using an Access (Jet) database as a data source for multithreaded applications, such as ASP.NET applications, is not recommended. If you must use Jet as a data source for an ASP.NET application, realize that ASP.NET applications connecting to an Access database can encounter connection problems.

The .NET Framework Data Provider for OLE DB does not support OLE DB version 2.5 interfaces. OLE DB Providers that require support for OLE DB 2.5 interfaces will not function correctly with the .NET Framework Data Provider for OLE DB. This includes the Microsoft OLE DB provider for Exchange and the Microsoft OLE DB provider for Internet Publishing.

The .NET Framework Data Provider for OLE DB does not work with the OLE DB provider for ODBC (MSDASQL). To access an ODBC data source using ADO.NET, use the .NET Framework Data Provider for ODBC.

.NET Framework Data Provider for OLE DB classes are located in the System.Data.OleDb namespace. The following code example shows how to include the System.Data.OleDb namespace in your applications.

.NET Framework Data Provider for ODBC

The .NET Framework Data Provider for ODBC (Odbc) uses the native ODBC Driver Manager (DM) to enable data access. The ODBC data provider supports both local and distributed transactions. For distributed transactions, the ODBC data provider, by default, automatically enlists in a transaction and obtains transaction details from Windows Component Services. For more information, see Transactions and Concurrency.

The following table shows the ODBC drivers tested with ADO.NET.

Driver
SQL Server
Microsoft ODBC for Oracle
Microsoft Access Driver (*.mdb)

.NET Framework Data Provider for ODBC classes are located in the System.Data.Odbc namespace.

The following code example shows how to include the System.Data.Odbc namespace in your applications.

Note

The .NET Framework Data Provider for ODBC requires MDAC 2.6 or a later version, and MDAC 2.8 SP1 is recommended. You can download MDAC 2.8 SP1 from the Data Access and Storage Developer Center.

.NET Framework Data Provider for Oracle

The .NET Framework Data Provider for Oracle (OracleClient) enables data access to Oracle data sources through Oracle client connectivity software. The data provider supports Oracle client software version 8.1.7 or a later version. The data provider supports both local and distributed transactions. For more information, see Transactions and Concurrency.

The .NET Framework Data Provider for Oracle requires Oracle client software (version 8.1.7 or a later version) on the system before you can connect to an Oracle data source.

.NET Framework Data Provider for Oracle classes are located in the System.Data.OracleClient namespace and are contained in the System.Data.OracleClient.dll assembly. You must reference both the System.Data.dll and the System.Data.OracleClient.dll when you compile an application that uses the data provider.

The following code example shows how to include the System.Data.OracleClient namespace in your applications.

Choosing a .NET Framework Data Provider

Depending on the design and data source for your application, your choice of .NET Framework data provider can improve the performance, capability, and integrity of your application. The following table discusses the advantages and limitations of each .NET Framework data provider.

Provider	Notes
.NET Framework Data Provider for SQL Server	Recommended for middle-tier applications that use Microsoft SQL Server. Recommended for single-tier applications that use Microsoft Database Engine (MSDE) or SQL Server. Recommended over use of the OLE DB provider for SQL Server (SQLOLEDB) with the .NET Framework Data Provider for OLE DB.
.NET Framework Data Provider for OLE DB	For SQL Server, the .NET Framework Data Provider for SQL Server is recommended instead of this provider. Recommended for single-tier applications that use Microsoft Access databases. Use of an Access database for a middle-tier application is not recommended.
.NET Framework Data Provider for ODBC	Recommended for middle and single-tier applications that use ODBC data sources.
.NET Framework Data Provider for Oracle	Recommended for middle and single-tier applications that use Oracle data sources.

EntityClient Provider

The EntityClient provider is used for accessing data based on an Entity Data Model (EDM). Unlike the other .NET Framework data providers, it does not interact directly with a data source. Instead, it uses Entity SQL to communicate with the underlying data provider. For more information, see EntityClient Provider for the Entity Framework.

See also

This chapter introduces Oracle Provider for OLE DB (OraOLEDB).

This chapter contains these topics:

1.1 Overview of OLE DB

OLE DB is an open standard data access methodology which utilizes a set of Component Object Model (COM) interfaces for accessing and manipulating different types of data. These interfaces are available from various database providers.

1.1.1 OLE DB Design

The design of OLE DB centers around the concept of a consumer and a provider. Figure 1-1 is an illustration of the OLE DB system. The consumer represents the traditional client. The provider places data into a tabular format and returns it to the consumer.

Figure 1-1 OLE DB Flow

Description of 'Figure 1-1 OLE DB Flow'

OLE DB Data Providers

OLE DB data providers are a set of COM components that transfer data from a data source to a consumer. An OLE DB Provider places that data in a tabular format in response to calls from a consumer. Providers can be simple or complex. A provider may return a table, it may allow the consumer to determine the format of that table, and it may perform operations on the data.

Each provider implements a standard set of COM interfaces to handle requests from the consumer. A provider may implement optional COM interfaces to provide additional functionality.

With the standard interfaces, any OLE DB consumer can access data from any provider. Because of COM components, consumers can access them in any programming language that supports COM, such as C++, Visual Basic, and Java.

OLE DB Data Consumers

The OLE DB data consumer is any application or tool that utilizes OLE DB interfaces of a provider to access a broad range of data.

1.2 Overview of OraOLEDB

Oracle Provider for OLE DB (OraOLEDB) is an OLE DB data provider that offers high performance and efficient access to Oracle data by OLE DB consumers.

In general, this developer's guide assumes that you are using OraOLEDB through OLE DB or ADO.

For sample code, the latest patches, and other technical information on the Oracle Provider for OLE DB, go to

With the advent of the .NET framework, support has been provided for using the OLEDB.NET Data Provider with OraOLEDB. With the proper connection attribute setting, an OLEDB.NET Data Provider can utilize OraOLEDB to access Oracle Database.

See Also:

'OLEDB.NET Data Provider Compatibility' for further information on support for OLEDB.NET Data Provider

1.3 System Requirements

Oracle 12c Oledb Provider Download

The following items are required on a system to use Oracle Provider for OLE DB:

• Windows Operating System:

  • 32-bit: Windows Vista (Business, Enterprise, and Ultimate Editions), Windows Server 2003, Windows Server 2003 R2, Windows 2000 or Windows XP Professional Edition.

  • 64 bit: Windows Vista x64 (Business, Enterprise, and Ultimate Editions), Windows Server 2003 x64, Windows Server 2003 R2 x64, or Windows XP x64.

  • 64-bit: Windows Server 2003 for Itanium-based systems.

• Access to an Oracle Database (Oracle 9.2 or later)

• Oracle Client release 11.1 or later and Oracle Net Services (included with Oracle Provider for OLE DB installation).

• Redistributable files provided with Microsoft Data Access Components (MDAC) 2.1 or higher are required by the provider. These files are available at the Microsoft Web site:

• Oracle Services for Microsoft Transaction Server release 11.1 or higher. This is required for consumers using Microsoft Transaction Server (MTS) or COM+.

1.4 OraOLEDB Installation

Oracle Provider for OLE DB is included as part of your Oracle installation. It contains the features and demos that illustrate how to use this product to solve real-world problems.

See Also:

The Oracle Database Installation Guide for Windows for installation instructions

During the installation process, the files listed in Table 1-1 are installed on the system. Some files have ver in their name to indicate the release version.

Table 1-1 Oracle Provider for OLE DB Files

File	Description	Location
OraOLEDBver.dll	Oracle Provider for OLE DB	ORACLE_BASEORACLE_HOMEbin
OraOLEDBrfcver.dll	Oracle rowset file cache manager	ORACLE_BASEORACLE_HOMEbin
OraOLEDBrmcver.dll	Oracle rowset memory cache manager	ORACLE_BASEORACLE_HOMEbin
OraOLEDBrstver.dll	Oracle rowset	ORACLE_BASEORACLE_HOMEbin
OraOLEDBgmrver.dll	Oracle ODBC SQL parser Citrix universal print driver download. Otherwise, contact your system administrator to get started.Note:Uninstall any other edition of Citrix Receiver for Windows that you might have installed on your device to install Citrix Receiver for Windows (Store) edition. Citrix Receiver provides access to virtual applications and desktops published on Windows and Linux operating systems, from anywhere, using any device.If your organization uses XenApp or XenDesktop, install Citrix Receiver on your device to get access to the remote Windows and Linux applications and desktops.After installation, configure Citrix Receiver to connect to your company's Citrix servers. If you know the URL, you can enter it yourself. Citrix Receiver provides access to virtual applications and desktops published on Windows and Linux operating systems, from anywhere, using any device.If your organization uses XenApp or XenDesktop, install Citrix Receiver on your device to get access to the remote Windows and Linux applications and desktops.After installation, configure Citrix Receiver to connect to your company's Citrix servers.	ORACLE_BASEORACLE_HOMEbin
OraOLEDBlangver.dll where lang is the required language	Language-specific resource DLL	ORACLE_BASEORACLE_HOMEbin
OraOLEDBpusver.dll	Property descriptions	ORACLE_BASEORACLE_HOMEbin
OraOLEDButlver.dll	OraOLEDB utility DLL	ORACLE_BASEORACLE_HOMEbin
OraOLEDBver.tlb	OraOLEDB type library	ORACLE_BASEORACLE_HOMEbin
OraOLEDB.h	OraOLEDB header file	ORACLE_BASEORACLE_HOMEoledbinclude
OraOLEDBver.lib	OraOLEDB library file	ORACLE_BASEORACLE_HOMEoledblib
OraOLEDBlang.msb where lang is the required language	Language-specific message file	ORACLE_BASEORACLE_HOMEoledbmesg
readme and documentation files	Release notes and online documentation	ORACLE_BASEORACLE_HOMEoledbdirectory
sample files	Sample code	ORACLE_BASEORACLE_HOMEoledbsamples

Oracle 11g Download 64 Bit

1.5 Component Certifications

Oracle Provider Download Speeds

Oracle provides support information for components on various platforms, lists compatible client and database versions, and identifies patches and workaround information.

Oracle Jce Provider Download

Find the latest certification information at:

Oracle Provider For Ole Db Download

You must register online before using OracleMetaLink. After logging into OracleMetaLink, select Product Lifecycle from the left column. From the Products Lifecycle page, click Certifications. Other Product Lifecycle options include Product Availability, Desupport Notices, and Alerts.