Introduction to TDP.NET

This chapter introduces Tibero Data Provider for .NET (TDP.NET).

Tibero Data Provider for .NET (TDP.NET) is a .NET data provider provided by Tibero. It works as an SQL interface between users' .NET applications and Tibero. It implements and provides not only core classes of ActiveX Data Objects .NET (ADO.NET) but also additional API.

TDP.NET has the following features.

  • Implemented by inheriting core objects of ADO.NET.

  • Managed driver written only in C#.

  • Users can write TDP.NET programs in .NET such as C# and Visual Basic .NET.

  • Based on .NET framework 2.0.

  • Can be run on both Windows 32-bit and 64-bit because built for any CPU.

Components

TDP.NET is an implementation of .NET data provider which is to use Tibero databases.

.NET data provider consists of the following 4 core objects of ADO.NET that are used to manipulate data.

Object

Description

Connection

Connect to a data source. TDP.NET's implementation is the TiberoConnection class.

Command

Executes a command against a data source. TDP.NET's implementation is the TiberoCommand class.

DataReader

Reads data from a data source. TDP.NET's implementation is the TiberoDataReader class.

DataAdapter

Populates a data set with data read from a data source or applies updated data to a data source. TDP.NET's implementation is the TiberoDataAdapter class.

TDP.NET inherits ADO.NET classes defined with the System.Data.Common namespace and includes classes for Tibero-specific types and functions.

Since TDP.NET is a managed driver written only in C#, it provides API for .NET applications although Tibero database server is not installed.


TDP.NET Assembly

Tibero.DataAccess.dll assembly provides the following two namespaces.

Tibero.DataAccess.Client

Includes ADO.NET implementation and classes provided by TDP.NET.

Tibero.DataAccess.Types

Includes TDP.NET type classes for Tibero types.


Differences with ODBC and OLEDB

There are following 3 ways to connect to Tibero database from a .NET environment: TDP.NET, ODBC, and OLEDB.

When using ODBC or OLEDB, a separate layer such as an ODBC driver (or MSDASQL, etc.) is required to connect to Tibero database. However, when using TDP.NET, no separate layer is necessary becausecode written in .NET can be converted to a protocol specific to Tibero database.

TDP.NET also supports Tibero-specific types and functions. That is, TDP.NET allows the most efficient access to Tibero database in a .NET environment.


System Requirements

The following are system requirements to use TDP.NET.

Operating system

Windows 32-bit and 64-bit. Since TDP.NET assembly is built for any CPU, it can run on both Windows 32-bit and 64-bit.

Microsoft .NET framework

.NET framework 2.0 or later. If a user's .NET framework is 4.0 or later, .NET framework 3.5 must be installed.


Default Path and Log Setting

The following describes the default path of TDP.NET assembly and how to set log.

Default path

After installing Tibero in a server, TDP.NET assembly is created in $TB_HOME/client/win32/lib, $TB_HOME/client/win64/lib.

Log setting

To write a log file, set the following two Windows environment variables.

Variable

Description

TDPNET_LOG_PATH

Path to a log file to create.

TDPNET_LOG_LVL

Log level. Currently, TRACE is supported.

Last updated