<?xml version="1.0" encoding="ISO-8859-1" ?>
<!--ATOM based XML document generated By OpenLink Virtuoso-->
<atom:feed xmlns:atom="http://www.w3.org/2005/Atom">
<atom:id>http://docs.openlinksw.com/virtuoso/vdbengine.html</atom:id>
<atom:title>Virtual Database Engine</atom:title>
<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengine.html" type="text/html" rel="alternate" />
<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengine.html" type="application/atom+xml" rel="self" />
<atom:subtitle>OpenLink Virtuoso Universal Server: Documentation</atom:subtitle>
 <atom:author>
  <atom:name>virtuoso.docs@openlinksw.com</atom:name>
  <atom:email>virtuoso.docs@openlinksw.com</atom:email>
  </atom:author>
<atom:updated>2009-11-05T00:30:50Z</atom:updated>
<atom:generator>OpenLink Software Documentation Team</atom:generator>
<atom:logo>http://docs.openlinksw.com/virtuoso/../images/misc/logo.jpg</atom:logo>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/thevdb.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Virtual Database (VDB) Engine<atom:link href="http://docs.openlinksw.com/virtuoso/thevdb.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Virtual Database (VDB) Engine</atom:title>
  <atom:content type="html" />
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginemc.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Oracle Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginemc.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Oracle Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An Oracle DBMS hosting the required Schema Objects needs to be available. In this section the Oracle Human Resources sample database will be used to demonstrate the process. An Oracle ODBC Driver is required for Linking the Oracle Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Oracle will be used in this section, for which a functional ODBC Data source name of &quot;ora10ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginepr.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Progress Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginepr.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Progress Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">A Progress DBMS hosting the required Schema Objects needs to be available. In this section, the isports sample database will be used to demonstrate the process. A Progress ODBC Driver is required to link the Progress Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Progress (SQL-92) will be used in this section, for which a functional ODBC Data source name of &quot;prs101c&quot; will be assumed to exist on the machine hosting the Virtuoso Server. An OpenLink Virtuoso Universal Server installation including the Virtuoso Universal Server and ADO.NET Entity Framework Provider is required. The Virtuoso components must be Release 5.10.x or above, this being the minimum version containing support for Microsoft Entity Frameworks.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbengineing.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Ingres Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengineing.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Ingres Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An Ingres DBMS hosting the required Schema Objects needs to be available. In this section the Ingres Tutorial sample database will be used to demonstrate the process. An Ingres ODBC Driver is required for Linking the Ingres Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Ingres will be used in this section, for which a functional ODBC Data source name of ingiima will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbengineinf.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Informix Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengineinf.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Informix Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An Informix DBMS hosting the required Schema Objects needs to be available. In this section the Informix stores_demo sample database will be used to demonstrate the process. An Informix ODBC Driver is required for Linking the Informix Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Informix will be used in this section, for which a functional ODBC Data source name of &quot;inf10ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginedb2.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access DB2 Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginedb2.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access DB2 Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An DB2 DBMS hosting the required Schema Objects needs to be available. In this section the DB2 sample database will be used to demonstrate the process. An DB2 ODBC Driver is required for Linking the DB2 Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for DB2 will be used in this section, for which a functional ODBC Data source name of &quot;db2v8ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginesyb.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Sybase Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginesyb.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Sybase Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An Sybase DBMS hosting the required Schema Objects needs to be available. In this section the Sybase pubs2 sample database will be used to demonstrate the process. An Sybase ODBC Driver is required for Linking the Sybase Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Sybase will be used in this section, for which a functional ODBC Data source name of &quot;syb15ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginemsql.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access MySQL Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginemsql.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access MySQL Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An MySQL DBMS hosting the required Schema Objects needs to be available. In this section the Northwind sample database will be used to demonstrate the process. An MySQL ODBC Driver is required for Linking the MySQL Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for MySQL will be used in this section, for which a functional ODBC Data source name of &quot;mysqlma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginepsql.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access PostgreSQL Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginepsql.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access PostgreSQL Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An PostgreSQL DBMS hosting the required Schema Objects needs to be available. In this section the PostgreSQL sample database will be used to demonstrate the process. An PostgreSQL ODBC Driver is required for Linking the PostgreSQL Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for PostgreSQL will be used in this section, for which a functional ODBC Data source name of &quot;ora10ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbengineodtjd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access ODBC to JDBC Bridge Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengineodtjd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access ODBC to JDBC Bridge Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An ODBC to JDBC Bridge DBMS hosting the required Schema Objects needs to be available. In this section we shall make and ODBC to JDBC bridge connection to another Virtuoso Northwind Demo database to demonstrate the process. An ODBC to JDBC Bridge Driver is required for Linking the ODBC to JDBC Bridge Schema Objects into the Virtuoso Server. The OpenLink ODBC to JDBC Bridge Driver will be used in this section, for which a functional ODBC Data source name of &quot;jdbcma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbengineodbcod.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access ODBC to ODBC Bridge Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbengineodbcod.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access ODBC to ODBC Bridge Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. An ODBC to ODBC Bridge DBMS hosting the required Schema Objects needs to be available. In this section we shall make and ODBC to ODBC bridge connection to another Virtuoso Northwind Demo database to demonstrate the process. An ODBC to ODBC Bridge Driver is required for Linking the ODBC to ODBC Bridge Schema Objects into the Virtuoso Server. The OpenLink ODBC to ODBC Bridge Driver will be used in this section, for which a functional ODBC Data source name of &quot;odbcma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginefirebd.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Firebird Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginefirebd.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Firebird Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. A Firebird DBMS hosting the required Schema Objects needs to be available. In this section the Firebird employee database will be used to demonstrate the process. A Firebird ODBC Driver is required for Linking the Firebird Schema Objects into the Virtuoso Server. The native Firebird ODBC Driver will be used in this section, for which a functional ODBC Data source name of &quot;fire&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
 <atom:entry>
  <atom:id>http://docs.openlinksw.com/virtuoso/vdbenginemsqls.html</atom:id>
  <atom:author>
    <atom:name>virtuoso.docs@openlinksw.com</atom:name>
    <atom:email>virtuoso.docs@openlinksw.com</atom:email>
   </atom:author>Using Microsoft Entity Frameworks to Access Microsoft SQL Server Schema Objects with Virtuoso<atom:link href="http://docs.openlinksw.com/virtuoso/vdbenginemsqls.html" type="text/html" rel="alternate" />
  <atom:published>2009-11-05T00:30:50Z</atom:published>
  <atom:title>Using Microsoft Entity Frameworks to Access Microsoft SQL Server Schema Objects with Virtuoso</atom:title>
  <atom:content type="html">The following prerequisites must be in place for this solution to be possible. A Microsoft SQL Server DBMS hosting the required Schema Objects needs to be available. In this document the Microsoft SQL Server Northwind sample database will be used to demonstrate the process. An Microsoft SQL Server ODBC Driver is required for Linking the Microsoft SQL Server Schema Objects into the Virtuoso Server. The OpenLink ODBC Driver for Microsoft SQL Server will be used in this section, for which a functional ODBC Data source name of &quot;sql2k5ma&quot; will be assumed to exist on the machine hosting the Virtuoso Server.</atom:content>
 </atom:entry>
</atom:feed>