This HTML5 document contains 40 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n11:this

foaf:made

n2:VirtIngresEntityFrameworkUsage

Subject Item

n7:this

sioc:creator_of

n2:VirtIngresEntityFrameworkUsage

Subject Item

n5:item

n4:services_of

n2:VirtIngresEntityFrameworkUsage

Subject Item

n19:this

sioc:creator_of

n2:VirtIngresEntityFrameworkUsage

Subject Item

n8:VOS

sioc:container_of

n2:VirtIngresEntityFrameworkUsage

atom:entry

n2:VirtIngresEntityFrameworkUsage

atom:contains

n2:VirtIngresEntityFrameworkUsage

Subject Item

n2:VirtIngresEntityFrameworkUsage

rdf:type

sioct:Comment atom:Entry

dcterms:created

2017-06-13T05:47:18.440058

dcterms:modified

2017-06-29T07:37:55.377644

rdfs:label

VirtIngresEntityFrameworkUsage

foaf:maker

n11:this n17:this

dc:title

VirtIngresEntityFrameworkUsage

opl:isDescribedUsing

n10:rdf

sioc:has_creator

n7:this n19:this

sioc:content

%VOSWARNING% %META:TOPICPARENT{name="VirtAdoNet35Provider"}% ---+ Using Microsoft Entity Frameworks to Access Ingres Schema Objects with Virtuoso This document details the steps required to provide Microsoft Entity Framework access to Ingres Schema Objects using the <nop>OpenLink Virtuoso Universal Server. This is achieved by linking the required Ingres 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 Ingres Schema objects linked into the Virtuoso Server. %TOC% ---++ Prerequisites The following must be in place to complete this exercise. 1 <b>Microsoft Visual Studio 2008 SP1 (or later)</b>%BR% Microsoft Visual Studio 2008 Service Pack 1 (or later) is required, as previous versions do not include the necessary Entity Framework support.%BR%%BR% 1 <b>Virtuoso ADO.NET Entity Framework Provider, v5.10 or later</b>%BR% 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.%BR%%BR% 1 <b>Virtuoso Universal Server, v5.10 or later</b>%BR% 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).%BR%%BR% 1 <b>ODBC Driver for Ingres</b>%BR% The Virtuoso Server uses an ODBC Driver for Ingres to link in the Ingres Schema Objects. The <b><nop>OpenLink Single-Tier ODBC Driver for Ingres</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of "<b><code>ingiima</code></b>" will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Ingres should work.%BR%%BR% 1 <b>Ingres DBMS</b>%BR% An Ingres 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 Ingres <b>Tutorial</b> database will be used to demonstrate the process.%BR%%BR% ---++ Tasks 1 <b>Ensure Ingres Primary Keys (PKs) are not nullable</b>%BR% 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 Ingres database schema before attempting to generate an EDM. In the case of the Ingres Tutorial database all primary keys are non nullable. Thus, this should not be an issue in this case.%BR%%BR% 1 <b>[[http://wikis.openlinksw.com/dataspace/owiki/wiki/UdaWikiWeb/InstallConfigODBC][Install and configure the <nop>OpenLink ODBC Driver for Ingres]]</b>%BR%%BR% 1 <b>[[VirtADOClientServInstall][Install and configure <nop>OpenLink Virtuoso Universal Server]]</b>%BR%%BR% 1 <b>[[VirtIngresLinkingObjects][Link Ingres tables and other schema objects into OpenLink Virtuoso]]</b>%BR%%BR% 1 <b>[[VirtIngresEDM][Create a Visual Studio-hosted Entity Data Model (EDM)]]</b>%BR%%BR%If entity-linking associations (i.e., Foreign Keys) are not automatically created (as they are not here with Ingres), the [[VirtIngresAssociations][associations must be created manually]].%BR%%BR% 1 <b>[[VirtEntityFrameworkIngresDatService][Use the EDM to create an Entity Frameworks-based ADO.NET Data Service]]</b>%BR%%BR% 1 <b>[[VirtIngresVisualStudioDataGridFormsApp][Use the EDM to create an Entity Frameworks-based Windows DataGrid Form Application]]</b>%BR% CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryIngres

sioc:id

5eb767d7cdb7e482a995d5d23a262468

sioc:link

n2:VirtIngresEntityFrameworkUsage

sioc:has_container

n8:VOS

n4:has_services

n5:item

atom:title

VirtIngresEntityFrameworkUsage

sioc:links_to

n2:CategoryIngres n2:VirtEntityFrameworkIngresDatService n2:VirtIngresEDM n2:CategoryDotNET n14:InstallConfigODBC n2:VirtIngresAssociations n2:VirtADOClientServInstall n2:CategoryVirtuoso n2:CategoryDocumentation n2:VirtIngresLinkingObjects n2:CategoryEntityFrameworks

atom:source

n8:VOS

atom:author

n11:this

atom:published

2017-06-13T05:47:18Z

atom:updated

2017-06-29T07:37:55Z

sioc:topic

n8:VOS