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

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

Subject Item

n2:VirtODBCEntityFrameworkUsage

rdf:type

atom:Entry sioct:Comment

dcterms:created

2017-06-13T05:49:57.095232

dcterms:modified

2017-06-13T05:49:57.095232

rdfs:label

VirtODBCEntityFrameworkUsage

foaf:maker

n19:this n5:this

dc:title

VirtODBCEntityFrameworkUsage

opl:isDescribedUsing

n8:rdf

sioc:has_creator

n6:this n14:this

sioc:content

%VOSWARNING% %META:TOPICPARENT{name="VirtAdoNet35Provider"}% ---+ Using Microsoft Entity Frameworks to Access Remote ODBC-accessible Schema Objects with Virtuoso, via an ODBC-to-ODBC Bridge This document details the steps required to provide Microsoft Entity Framework access to remote ODBC-accessible Schema Objects using the <nop>OpenLink Virtuoso Universal Server. This is achieved by linking the remote Schema Objects into Virtuoso using its built-in Virtual Database engine, through an ODBC-to-ODBC Bridge, and then using the Virtuoso ADO.NET Entity Framework provider to query the remote 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 ODBC Data Sources</b>, also known as an <b>ODBC-to-ODBC Bridge</b>%BR% The Virtuoso Server uses a network-enabled ODBC-to-ODBC Bridge to link in the non-networked ODBC-accessible Schema Objects. The <b><nop>OpenLink Multi-Tier ODBC Driver for ODBC Data Sources</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of "<b><code>odbcma</code></b>" will be assumed to exist on the machine hosting the Virtuoso Server. Any network-enabled ODBC compliant driver for non-networked ODBC data sources should work.%BR%%BR% 1 <b>ODBC-accessible DBMS</b> and its associated <b>ODBC Driver</b>%BR% A ODBC-accessible DBMS hosting the required Schema Objects needs to be available, and a ODBC Driver for same must be available to the ODBC-to-ODBC Bridge. Specific requirements depend on the target DBMS, the ODBC driver, and the ODBC-to-ODBC Bridge. In this document, a remote Microsoft Access <b>Northwind</b> database will be used to demonstrate the process, through the <b>Microsoft ODBC Driver for Access</b>.%BR%%BR% ---++ Tasks 1 <b>Ensure ODBC-accessible DBMS Primary Keys (PKs) are not nullable</b>%BR% The Visual Studio 2008 Entity Data Model (EDM) requires that all primary keys are *NOT* Nullable. Visual Studio 2008 will fail to generate an EDM if any are. Therefore, ensure any primary keys to be used are defined as not nullable in the ODBC-accessible database schema before attempting to generate an EDM. In the case of the Microsoft Access Northwind database, all primary keys are non nullable. Thus, this should not be an issue.%BR%%BR% 1 <b>[[http://wikis.openlinksw.com/dataspace/owiki/wiki/UdaWikiWeb/InstallConfigODBC][Install and configure the <nop>OpenLink ODBC Driver for ODBC Data Sources]]</b>%BR%%BR% 1 <b>[[VirtADOClientServInstall][Install and configure <nop>OpenLink Virtuoso Universal Server]]</b>%BR%%BR% 1 <b>[[VirtOODBCLinkingObjects][Link ODBC-accessible tables and other schema objects into OpenLink Virtuoso]]</b>%BR%%BR% 1 <b>[[VirtOODBCEDM][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 Access), the [[VirtOODBCAssociations][associations must be created manually]].%BR%%BR% 1 <b>[[VirtEntityFrameworkOODBCDatService][Use the EDM to create an Entity Frameworks-based ADO.NET Data Service]]</b>%BR%%BR% 1 <b>[[VirtODBCVisualStudioDataGridFormsApp][Use the EDM to create an Entity Frameworks-based Windows DataGrid Form Application]]</b>%BR% CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryODBC CategoryODBCODBCBridge

sioc:id

eef44c7baf6ed1a1f7a60ca2cb6b97a9

sioc:link

n2:VirtODBCEntityFrameworkUsage

sioc:has_container

n10:VOS

n16:has_services

n17:item

atom:title

VirtODBCEntityFrameworkUsage

sioc:links_to

n2:VirtOODBCLinkingObjects n2:VirtADOClientServInstall n2:VirtOODBCAssociations n2:CategoryODBC n2:VirtEntityFrameworkOODBCDatService n2:CategoryDotNET n2:CategoryDocumentation n13:InstallConfigODBC n2:CategoryEntityFrameworks n2:VirtODBCVisualStudioDataGridFormsApp n2:CategoryVirtuoso n2:VirtOODBCEDM n2:CategoryODBCODBCBridge

atom:source

n10:VOS

atom:author

n5:this

atom:published

2017-06-13T05:49:57Z

atom:updated

2017-06-13T05:49:57Z

sioc:topic

n10:VOS