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

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

Subject Item

n4:this

foaf:made

n2:VirtOODBCLinkingObjects

Subject Item

n11:item

n10:services_of

n2:VirtOODBCLinkingObjects

Subject Item

n15:this

sioc:creator_of

n2:VirtOODBCLinkingObjects

Subject Item

n9:ODS

sioc:container_of

n2:VirtOODBCLinkingObjects

atom:entry

n2:VirtOODBCLinkingObjects

atom:contains

n2:VirtOODBCLinkingObjects

Subject Item

n2:VirtOODBCLinkingObjects

rdf:type

atom:Entry sioct:Comment

dcterms:created

2017-06-13T06:02:36.179235

dcterms:modified

2017-06-29T07:34:19.674714

rdfs:label

VirtOODBCLinkingObjects

foaf:maker

n4:this n32:this

dc:title

VirtOODBCLinkingObjects

opl:isDescribedUsing

n19:rdf

sioc:has_creator

n14:this n15:this

sioc:attachment

n16:png n17:png n20:png n21:png n22:png n23:png n25:png n26:png n27:png n28:png n29:png n30:png n31:png

sioc:content

%VOSWARNING% %META:TOPICPARENT{name="VirtLinkRemoteTables"}% ---+ Linking ODBC-accessible Database Objects (Tables, Views, and Stored Procedures) into Virtuoso ---++ Prerequisites * <b>Virtuoso Universal Server, Commercial Edition</b>%BR% Virtuoso Universal Server Release 6.x or later is recommended, optimally the latest version available.%BR%%BR% * <b>ODBC Driver for RDBMS or other Data Source</b>%BR% The Virtuoso Server uses an ODBC Driver for the RDBMS or other Data Source to link in the external Schema Objects (Tables, Views, and Stored Procedures). The Microsoft-supplied, Windows-bundled <b><nop>ODBC Driver for Microsoft Access</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 ODBC compliant driver should work.%BR%%BR% * <b>RDBMS or other Data Source</b>%BR% A DBMS hosting the required Schema Objects (Tables, Views, and Stored Procedures) needs to be available. This may be on any host which is TCP/IP accessible from the Virtuoso Server host. In this document, the Microsoft Access <b>Northwind</b> sample database will be used to demonstrate the process.%BR%%BR% ---++ Steps 1 Start the Virtuoso Web User Interface. %BR%%BR%<img src="%ATTACHURLPATH%/VirtWebHome.png" style="wikiautogen"/>%BR%%BR% 1 Select the *Conductor* link in the left frame and login as the *dba* user. %BR%%BR%<img src="%ATTACHURLPATH%/VirtConductor.png" style="wikiautogen"/>%BR%%BR% 1 Select the *Databases* -> *External Data Source* -> *Data Sources* tab menu items. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC1.png" style="wikiautogen"/>%BR%%BR% 1 Select the *Connect* button for the *odbcma* ODBC to ODBC Bridge DSN. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC2.png" style="wikiautogen"/>%BR%%BR% 1 On succesful connection, select the *Link Objects* button to obtain a list of available tables. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC3.png" style="wikiautogen"/>%BR%%BR% 1 Select all the tables that are part of the *Northwind* catalog. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC4.png" style="wikiautogen"/>%BR%%BR% 1 Change the Catalog for each table to be *NWIND* using the *Set All* button. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC5.png" style="wikiautogen"/>%BR%%BR% 1 All the catalog names are changed to be *NWIND*. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC6.png" style="wikiautogen"/>%BR%%BR% 1 Select the *Link* button to link the selected tables into Virtuoso. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC7.png" style="wikiautogen"/>%BR%%BR% 1 On completion of the link process, the tables will be displayed in the *External Linked Objects* tab. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC8.png" style="wikiautogen"/>%BR%%BR% 1 The linked tables can be queried by clicking on the hyperlink in the *Local Name* column of the *External Linked Objects* tab above. This loads the Virtuoso *Interactive SQL* interface with the required SQL *Select* for retrieving the remote table data. We shall use the *NWIND.odbcma.Customers* table to demonstrate this. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC10.png" style="wikiautogen"/>%BR%%BR% 1 Click the *Execute* button to run the query and retrieve the results from the remote table. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC11.png" style="wikiautogen"/>%BR%%BR% 1 The tables can also be viewed as part of the Virtuoso *SQL Schema Objects* under the *NWIND* catalog name. %BR%%BR%<img src="%ATTACHURLPATH%/VirtLinkODBC9.png" style="wikiautogen"/>%BR%%BR% The link process is now complete, enabling the tables to be queried as if local to the Virtuoso instance. ---++ Related * [[VOSSQL2RDF][Mapping SQL Data to Linked Data Views]] * [[VirtODBCEntityFrameworkUsage][ Using Microsoft Entity Frameworks to Access Remote ODBC-accessible Schema Objects (Tables, Views, and Stored Procedures) with Virtuoso, via an ODBC-to-ODBC Bridge]] CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryODBC CategoryODBCODBCBridge

sioc:id

1e2091c2630c6d8639c23fa0a635ead2

sioc:link

n2:VirtOODBCLinkingObjects

sioc:has_container

n9:ODS

n10:has_services

n11:item

atom:title

VirtOODBCLinkingObjects

sioc:links_to

n7:VOSSQL2RDF n7:VirtODBCEntityFrameworkUsage n2:CategoryODBCODBCBridge n7:CategoryEntityFrameworks n2:CategoryVirtuoso n2:CategoryODBC n7:CategoryDotNET n2:CategoryDocumentation

atom:source

n9:ODS

atom:author

n4:this

atom:published

2017-06-13T06:02:36Z

atom:updated

2017-06-29T07:34:19Z

sioc:topic

n9:ODS

Subject Item

n14:this

sioc:creator_of

n2:VirtOODBCLinkingObjects