Not logged in : Login

About: VirtODBCEntityFrameworkUsage     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : atom:Entry, within Data Space : www.openlinksw.com associated with source document(s)
QRcode icon
http://www.openlinksw.com/describe/?url=http%3A%2F%2Fwww.openlinksw.com%2Fdataspace%2Fdav%2Fwiki%2FVOS%2FVirtODBCEntityFrameworkUsage

AttributesValues
has container
Date Created
maker
topic
described by
seeAlso
Date Modified
link
id
  • 2cc2d5b51c67c21c843bc9983e6dcf08
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
Title
  • VirtODBCEntityFrameworkUsage
has creator
is described using
atom:source
atom:updated
  • 2014-11-04T16:01:48Z
atom:title
  • VirtODBCEntityFrameworkUsage
links to
atom:author
label
  • VirtODBCEntityFrameworkUsage
topic
atom:published
  • 2010-02-01T13:20:58Z
type
is topic of
Faceted Search & Find service v1.17_git63 as of Apr 23 2021


Alternative Linked Data Documents: iSPARQL | ODE     Content Formats:       RDF       ODATA       Microdata      About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3322 as of Jun 3 2021, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (30 GB total memory)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2021 OpenLink Software