Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
Overview
Programmer's Guide > OpenAccess ORM Classic (Old API) > Programming With OpenAccess > Low-level Driver > Overview

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

Telerik OpenAccess ORM uses a low-level driver for the actual communication with the database system

The following table provides an overview:

Name Description

genericADO2

a�� driver using SqlClient or OracleClient

a�� supports SQL Server 2005, MySQL 5.0, Advanatage Database Server 8.1, SQLExpress, SQL Anywhere Server and Firebird

a�� supports Oracle 9i and higher

a�� new as of OpenAccess ORM 4.0 (i.e for 4.0, 4.1, 4.2 and 4.3 versions)

a�� supports .NET 1.1 and .NET 2.0

Odp

a�� .driver using ODP.NET (Oracle Data Provider)

a�� supports Oracle 9i and higher

a�� supports .NET 1.1 and .NET 2.0

The reason for this variety is that OpenAccess ORM extensively uses multiple active result sets (MARS) for performance reasons. This feature is not a ADO.NET feature but a server feature; MARS is supported by Oracle and MS SQL Server 2005. However, to make use of that feature the driver must support it, this support has been introduced in the SqlClient and OracleClient in .NET 2.0.

The following matrix shows the supported combinations, the default appears in bold if more than one driver is available for a combination:

Database \ .NET framework

.NET 1.1

.NET 2.0

SQL Server 2000 and MSDE

genericADO

genericADO*

SQL Server 2005 and SQLExpress

 

genericADO

genericADO2

MySQL

genericADO

genericADO2

Advantage Database Server

genericADO

genericADO2

SQL Anywhere Server

 

genericADO2

Oracle 9i and higher

odp

odp

genericADO2

Firebird

 

genericADO2

* must be explicitly enabled, otherwise an exception will be thrown

The implementation to access an Oracle database via ODP .NET is in the genericADO2 driver. You only need to specify "driver=odp" in the backend configurations section to use this driver (refer to Backend settings for more information).