Quick Start: Progress DataDirect Connect for ADO.NET Oracle ADO.NET Entity Framework Data Provider

Transcription

1 Quick Start: Progress DataDirect Connect for ADO.NET Oracle ADO.NET Entity Framework Data Provider The following basic information enables you to connect with and test your Progress DataDirect Connect for ADO.NET Oracle ADO.NET Entity Framework data provider immediately after installation. For installation instructions, please see the DataDirect Connect for ADO.NET Installation Guide. Code examples in this document assume you are using C# and Visual Studio. Connecting to a Database Once a DataDirect Connect for ADO.NET data provider is installed, you can connect from your application to your database with a connection string using either the DataDirect Oracle data provider-specific objects or the Common Programming Model. Using the Common Programming Model 1 Check the beginning of your application. Ensure that the.net Framework namespace is present. // Access Oracle using System.Data; using System.Data.Common; 2 Add the connection information for your server and exception handling code and close the connection. DbProviderFactory factory = DbProviderFactories("DDTek.Oracle"); DbConnection Conn = factory.createconnection(); Conn.CommandText = "host=accounting1;port=1521;service Name=test;User ID=test01;Password=test01"; try { Conn.Open(); Console.WriteLine("Connection successful!"); catch (Exception ex) { // Connection failed Console.WriteLine(ex.Message); // Close the connection Conn.Close(); Using the DataDirect Common Assembly You can optionally include the DataDirect Common Assembly if you want to use features such as DataDirect Bulk Load that conforms to the Common Programming Model. The following example illustrates how to use the DataDirect Common Programming Assembly in an application developed in Visual Studio using C# and the Common Programming Model.

2 1 Check the beginning of your application. Ensure that the.net Framework and the DataDirect Common Assembly namespaces are present. // Access Oracle using System.Data; using System.Data.Common; using DDTek.Data.Common; 2 Add the connection information for your server and exception handling code and close the connection. // This code does a bulk copy operation from one Oracle database // to another DbProviderFactory factory = DbProviderFactories("DDTek.Oracle"); DbConnection Conn1 = factory.createconnection(); Conn1.ConnectionString = "... Oracle Server..."; Conn1.Open(); DbCommand command = "SELECT ProductID, Name FROM Products"; DbDataReader reader = command.executereader(); using (DbConnection Conn2 = factory.createconnection()) Conn2.ConnectionString = "... Oracle Server..."; Conn2.Open(); using (DbBulkCopy bulkcopy = new DbBulkCopy(Conn2) { bulkcopy.destinationtable = "ProductsMirror"; try { bulkcopy.writetoserver(reader); catch { Console.WriteLine(ex.Message); Provider Schema Attribute Provider is an attribute of the Schema element in the storage model file of an Entity Data Model (EDM). The storage model file is written in the store schema definition language (SSDL). The Entity Data Model wizard assigns the value when you select the Oracle data provider. If you are manually defining an Entity Data Model, assign the string DDTek.Oracle to the Provider attribute of the Schema element. Note this is typically generated for you: <Schema Namespace="AdventureWorksModel.Store" Alias="Self" Provider="DDTek.Oracle" ProviderManifestToken="2005" xmlns:store=" chemagenerator" xmlns="

3 Using the Data Provider with the ADO.NET Entity Framework The Oracle data provider can be used with applications that use the standard ADO.NET features, or with the ADO.NET Entity Framework. Before You Start In order to connect to the database server using the Oracle ADO.NET Entity Framework data provider, the server and Visual Studio 2008 Service Pack 1 must be running. In this tutorial it is assumed that you already have the database objects created. Creating a Model The Entity Framework creates a model of your data in Visual Studio. 1 Create a new Windows Console application in Visual Studio 2 In the Solution Explorer, right-click on the project and select Add / New Item. 3 Select ADO.NET Entity Data Model, and then click Add. 4 The Entity Data Model Wizard appears. Select Generate from database, and then click Next. 5 Click New Connection... to create a new connection. a. On the Choose Data Source window, select Other in the Data source list, then DataDirect Connect for ADO.NET Oracle Data Provider in the Data provider drop-down list. b. Click Continue. c. The Connection Properties window appears. Provide the necessary connection information, and then click OK.

4 6 The Wizard creates an Entity connection string. a. If the radio buttons are selectable, select Yes, include the sensitive data in the connection string. b. In the Save entity connection settings... field, type a name for the name of the main data access class, or accept the default. c. Click Next.

5 7 Select the database objects that will be used in the model.

6 8 Click Finish. The model is generated and opened in the Model Browser. Testing the Connection You can test the connection using a small C# application in Visual Studio. 1 Create a small Windows test application (refer to the Microsoft.NET Framework documentation). 2 Add a button to the default form that is created for you. 3 Follow the steps in the Connecting to a Database section above, making sure that you modify the connection string values for your Oracle server, Password, user ID, and Service Name. Add the code shown in Step 5 of that procedure to the button s click event.

7 4 Save the test application. 5 To test the connection, click the button in the test application. Tuning the Data Provider for Optimal Performance To tune the data provider for optimal performance, run the DataDirect Connect for ADO.NET Performance Tuning Wizard, which is available in Visual Studio. The Performance Tuning Wizard leads you step-bystep through a series of questions about your application. Based on your answers, the Performance Tuning Wizard provides the optimal settings for performance-related connection string options. Starting the Performance Tuning Wizard To start the Performance Tuning Wizard: 1. In the Visual Studio menu bar, select Tools. 2. Select DataDirect Technologies / Run DataDirect Performance Wizard. You can also start the Performance Tuning Wizard by right-clicking an existing connection in the Server Explorer. Tuning Performance with the Performance Tuning Wizard After you start the Performance Tuning Wizard, a Welcome window appears. Click Next to start the process and select a data provider. When you have answered all questions for a data provider, results are displayed in the Result window. You can use the results in the following ways: Copy the generated values for connection string options into an existing connection string. Create a new connection with the Performance Tuning Wizard connection string values. Generate a new application pre-configured with a connection string optimized for your environment. The Performance Tuning Wizard provides options to select the type of application and the version of ADO.NET code that you want to use. Using Microsoft Enterprise Library Patterns and Practices Using Microsoft Enterprise Library patterns can simplify application development by wrapping common tasks, such as data access, into portable code that makes it easier to move your application from one DBMS to another. To use features of the Enterprise Library with your data provider, download Microsoft Enterprise Library 4.1 (October 2008) from The installation by default includes the documentation for the Enterprise Library 4.1. The classes in the Data Access Application Blocks (DAABs) provide access to the most frequently used features of ADO.NET. Applications can use the DAABs for tasks such as passing data through application layers and returning changed data back to the database. Using DAABs eliminates the need to keep writing the same data access tasks for each new or revised application, so you can spend your time more productively. The DataDirect Connect for ADO.NET data providers can be used with Data Access Application Blocks. Refer to the technical brief, Using the Microsoft Enterprise Library Data Access Application Block (DAAB) in Your Application at for more information.

8 Applications that use the standard Logging Application Block (LAB) and design patterns can quickly display the SQL generated as part of the DataDirect Connect Oracle data provider for ADO.NET Entity Framework. In particular, the LAB is useful if you need to filter logging messages based on category or priority, if you need to format the messages, or if you need to change the destination of the message without changing the application code. The Oracle data provider includes a set of LAB customizations that are useful for the ADO.NET Entity Framework Progress Software Corporation. All rights reserved. 08/09, 3.3