Chapter 19. EDB Connector/.NET

Table of Contents
19.1. .NET Data Provider Types
19.2. Installing EDB Connector/.NET
19.3. Setting up EDB Connector/.NET
19.3.1. Setting up EDB Connector/.NET with Visual Studio .NET
19.3.2. Setting up EDB Connector/.NET without Visual Studio .NET
19.3.3. Setting up EDB Connector/.NET with Mono
19.4. Data Provider Components
19.5. Performing common database tasks
19.6. Opening a Database Connection
19.6.1. Opening a Database Connection using ASP.NET
19.6.2. Opening a Database Connection from a Console Application
19.6.3. Opening a Database Connection from a Windows Form Application
19.6.4. Opening a Database Connection - Explanation
19.7. Retrieving Database Records
19.8. Retrieving a Single Database Records
19.9. Parameterized Queries
19.10. Inserting Records in a Database
19.11. Deleting Records in a Database
19.12. Using SPL Stored Procedures in your .NET Application
19.12.1. Executing a Stored Procedure without any Parameters
19.12.2. Executing a Stored Procedure with IN Parameters
19.12.3. Executing a Stored Procedure with OUT Parameters
19.12.4. Executing a Stored Procedure with INOUT Parameters
19.13. Using Connection Pooling

The Microsoft .NET platform is used by many software developers for implementing software solutions and ADO.NET is the data access API that enables database connectivity for.NET applications. ADO.NET currently ships with a couple of .NET data providers allow us to connect to a data source, and to execute SQL commands against it. The .NET data providers that enables users to connect to an EnterpriseDB database via their .NET applications is known as EDB Connector/.NET

19.1. .NET Data Provider Types

ADO.NET enables access to a variety of different data sources, including relational databases such as Microsoft SQL Server, Oracle, and Microsoft Access, as well as other data sources such as Microsoft Excel, Outlook, and text files.

The two Data Providers shipped with the .NET Framework are :

  1. OLEDB

  2. Microsoft SQL Server

Other providers are also available-for example, Oracle has developed its own .NET data provider for Oracle.

Similarly EnterpriseDB has developed its own data provider to access an EnterpriseDB database. The provider named "EDB Connector/.NET" accesses the underlying EDB data store directly and offers the best performance, broadest functionality, and support for EDB-specific features.