| content
| - %META:TOPICPARENT{name="VirtAdoNet35Provider"}%
---+ Using Microsoft Entity Frameworks to Access Microsoft SQL Server Schema Objects with Virtuoso
This document details the steps required to provide Microsoft Entity Framework access to Microsoft SQL Server Schema Objects using the <nop>OpenLink Virtuoso Universal Server. This is achieved by linking the required Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server</b>%BR%
The Virtuoso Server uses an ODBC Driver for Microsoft SQL Server to link in the Microsoft SQL Server Schema Objects. The <b><nop>OpenLink Single-Tier ODBC Driver for Microsoft SQL Server</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of "<code>sql2k5ma</code>" will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Microsoft SQL Server should work.%BR%%BR%
1 <b>Microsoft SQL Server DBMS</b>%BR%
A Microsoft SQL Server 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 <b>Microsoft SQL Server Northwind</b> sample database will be used to demonstrate the process.%BR%%BR%
---++ Tasks
1 <b>Ensure Microsoft SQL Server 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. Thus ensure any tables to be used are defined as not nullable in the Microsoft SQL Server database schema before attempting to generate an EDM. In the case of the Microsoft SQL Server Northwind database all tables are not 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 Microsoft SQL Server]]</b>%BR%%BR%
1 <b>[[VirtADOClientServInstall][Install and configure <nop>OpenLink Virtuoso Universal Server]]%BR%%BR%
1 <b>[[VirtMSSQLLinkingObjects][Link Microsoft SQL Server tables and other schema objects into OpenLink Virtuoso]]%BR%%BR%
1 <b>[[VirtSQLEDM][Create a Visual Studio-hosted Entity Data Model (EDM)]]%BR%%BR%
1 <b>[[VirtEntityFrameworkSQLDatService][Use the EDM to create an Entity Frameworks-based ADO.NET Data Service]]%BR%
CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryMSSQLServer
- %META:TOPICPARENT{name="VirtAdoNet35Provider"}%
---+ Using Microsoft Entity Frameworks to Access Microsoft SQL Server Schema Objects with Virtuoso
This document details the steps required to provide Microsoft Entity Framework access to Microsoft SQL Server Schema Objects using the <nop>OpenLink Virtuoso Universal Server. This is achieved by linking the required Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server</b>%BR%
The Virtuoso Server uses an ODBC Driver for Microsoft SQL Server to link in the Microsoft SQL Server Schema Objects. The <b><nop>OpenLink Multi-Tier ODBC Driver for Microsoft SQL Server</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of "<code>sql25ma</code>" will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Microsoft SQL Server should work.%BR%%BR%
1 <b>Microsoft SQL Server DBMS</b>%BR%
A Microsoft SQL Server 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 <b>Microsoft SQL Server Northwind</b> sample database will be used to demonstrate the process.%BR%%BR%
---++ Tasks
1 <b>Ensure Microsoft SQL Server 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. Thus ensure any tables to be used are defined as not nullable in the Microsoft SQL Server database schema before attempting to generate an EDM. In the case of the Microsoft SQL Server Northwind database all tables are not 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 Microsoft SQL Server]]</b>%BR%%BR%
1 <b>[[VirtADOClientServInstall][Install and configure <nop>OpenLink Virtuoso Universal Server]]%BR%%BR%
1 <b>[[VirtMSSQLLinkingObjects][Link Microsoft SQL Server tables and other schema objects into OpenLink Virtuoso]]%BR%%BR%
1 <b>[[VirtSQLEDM][Create a Visual Studio-hosted Entity Data Model (EDM)]]%BR%%BR%
1 <b>[[VirtEntityFrameworkSQLDatService][Use the EDM to create an Entity Frameworks-based ADO.NET Data Service]]%BR%
CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryMSSQLServer
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)