Using Microsoft Entity Frameworks to Access Informix Schema Objects with Virtuoso This document details the steps required to provide Microsoft Entity Framework access to Informix Schema Objects using the OpenLink Virtuoso Universal Server. This is achieved by linking the required Informix Schema objects into Virtuoso using its built-in Virtual Database engine and then using the Virtuoso ADO.NET Entity Framework provider to query the remote Informix Schema objects linked into the Virtuoso Server. Prerequisites The following must be in place to complete this exercise. Microsoft Visual Studio 2008 SP1 (or later) Microsoft Visual Studio 2008 Service Pack 1 (or later) is required, as previous versions do not include the necessary Entity Framework support. Virtuoso ADO.NET Entity Framework Provider, v5.10 or later The ADO.NET Entity Framework Provider must be installed on the Visual Studio development and deployment host(s). Version 5.10.x or later is required, as previous versions do not include the necessary Entity Frameworks support. Virtuoso Universal Server, v5.10 or later Virtuoso Universal Server Release 5.10 or later is required, as previous versions do not include the necessary Entity Frameworks support. This may be on any host which is TCP/IP accessible from the Visual Studio development and deployment host(s). ODBC Driver for Informix The Virtuoso Server uses an ODBC Driver for Informix to link in the Informix Schema Objects. The OpenLink Single-Tier ODBC Driver for Informix will be used in this document, and a functional ODBC Data Source Name (DSN) of "inf10ma" will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Informix should work. Informix DBMS An Informix DBMS hosting the required Schema Objects needs to be available. This may be on any host which is TCP/IP accessible from the Virtuoso Server host. In this document, the Informix stores_demo database will be used to demonstrate the process. Tasks Ensure Informix Primary Keys (PKs) are not nullable The Visual Studio 2008 Entity Data Model (EDM) requires that all primary keys are NOT Nullable, and will fail to generate an EDM if any are. Therefore, ensure any tables to be used are defined as not nullable in the Informix database schema before attempting to generate an EDM. In the case of the Informix stores_demo database, many tables have primary keys that are nullable, so these will need to be redeclared.This is possible using dbaccess. However, care needs to be taken, particularly with the following cases, where the additional primary and foreign key constraints that are removed will have to be manually recreated — Amending a PK field to be not nullable can result in the primary key constraint being removed. When a primary key is referenced by a foreign key constraint, amending the PK field to be not nullable results in the foreign key constraint being removed. Install and configure the OpenLink ODBC Driver for Informix Install and configure OpenLink Virtuoso Universal Server Link Informix tables and other schema objects into OpenLink Virtuoso Create a Visual Studio-hosted Entity Data Model (EDM) Use the EDM to create an Entity Frameworks-based ADO.NET Data Service Use the EDM to create an Entity Frameworks-based Windows DataGrid Form Application CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryInformix