www.openlinksw.com
docs.openlinksw.com

Book Home

Contents
Preface

ADO.NET Data Providers

Architecture
Managed Data Provider Unmanaged Data Provider
Developing .NET Data Provider Application
OpenLink .NET Data Providers Connect String Attributes
OpenLink .NET Data Providers Class Implementation
OpenLink.Data Namespace
Known Issues
.Net Provider Test Program
New Features

6.1. Architecture

From the outset one of the main design goals of the .Net Data Provider was to implement a generic client layer enabling the re-use of our existing data access components for connecting to remote data sources. This has been achieved with both our Managed and Unmanaged .Net Data Providers, each of which have a common namespace that eliminates the need to recompile applications should the need arise to change the remote data source.

6.1.1. Managed Data Provider

The UDA managed .NET Data Provider delivers robust and secure data connectivity across all Databases support in the Universal Data Access suite, including all major databases - Microsoft SQL Server, Oracle, DB2, Sybase, Ingres II, Informix and Progress. The .NET Data Provider is built with managed code, enabling it to running completely within the .NET Framework runtime delivering better security and performance. This Generic managed .Net Data Provider connects to the remote data source via one of two forms currently:


6.1.2. Unmanaged Data Provider

The UDA Unmanaged .NET Data Provider enables connectivity to any ODBC Data Source by acting as a Bridge between ADO.Net and ODBC. This Provider is provided as a stop-gap solution enabling connectivity to Data source for which managed .Net Providers are not already available as indicated in the diagram below, and as such does not provide the benefits of security and performance available from its Managed counterpart:

Figure: 6.1.2.1. Unmanaged ODBC .Net Data Provider
Unmanaged ODBC .Net Data Provider