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

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

Subject Item

n26:this

foaf:made

n2:VirtSybaseLinkingObjects

Subject Item

n18:item

n19:services_of

n2:VirtSybaseLinkingObjects

Subject Item

n30:this

sioc:creator_of

n2:VirtSybaseLinkingObjects

Subject Item

n7:ODS

sioc:container_of

n2:VirtSybaseLinkingObjects

atom:entry

n2:VirtSybaseLinkingObjects

atom:contains

n2:VirtSybaseLinkingObjects

Subject Item

n2:VirtSybaseLinkingObjects

rdf:type

atom:Entry sioct:Comment

dcterms:created

2017-06-13T06:04:03.609459

dcterms:modified

2017-06-29T07:34:37.446361

rdfs:label

VirtSybaseLinkingObjects

foaf:maker

n26:this n29:this

dc:title

VirtSybaseLinkingObjects

opl:isDescribedUsing

n24:rdf

sioc:has_creator

n27:this n30:this

sioc:attachment

n5:png n6:png n9:png n10:png n12:png n13:png n14:png n15:png n16:png n20:png n21:png n22:png n32:png n33:png n34:png n35:png

sioc:content

%VOSWARNING% %META:TOPICPARENT{name="VirtLinkRemoteTables"}% ---+ Linking Sybase Database Objects (Tables, Views, and Stored Procedures) 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 Sybase</b>%BR% The Virtuoso Server uses an ODBC Driver for Sybase to link in the Sybase Schema Objects (Tables, Views, and Stored Procedures). The <b><nop>OpenLink Multi-Tier ODBC Driver for Sybase</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of <b><code><nowiki>syb12ma-pub2</nowiki></code></b> will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Sybase should work.%BR%%BR% * <b>Sybase DBMS</b>%BR% A Sybase 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 Sybase <b>pubs2</b> sample database will be used to demonstrate the process.%BR%%BR% ---++ Steps 1 Load the HTTP-based Virtuoso User Interface in your browser. %BR%%BR%<a href="%ATTACHURLPATH%/VirtWebHome.png"><img src="%ATTACHURLPATH%/VirtWebHome.png" style="wikiautogen" width="600px" alt="" /></a>%BR%%BR% 1 Click the <b>Conductor</b> link in the left-side navbar, and log in as a user with DBA privileges, such as the default <b><code>dba</code></b> user. %BR%%BR%<a href="%ATTACHURLPATH%/VirtConductor.png"><img src="%ATTACHURLPATH%/VirtConductor.png" style="wikiautogen" width="600px" alt="VirtConductor.png" /></a>%BR%%BR% 1 Drill down to the <b>Databases</b> -> <b>External Data Source</b> -> <b>Data Sources</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb01.png"><img src="%ATTACHURLPATH%/VirtLinkSyb01.png" style="wikiautogen" width="600px" alt="VirtLinkSyb01.png" /></a>%BR%%BR% 1 Locate the DSN for the desired remote data source (we're using <b><code><nowiki>syb12ma-pub2</nowiki></code></b> for this example). If not yet connected to the DSN, click <b>Connect</b>, and input your user credentials for the remote data source. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb02.png"><img src="%ATTACHURLPATH%/VirtLinkSyb02.png" style="wikiautogen" width="600px" alt="VirtLinkSyb02.png" /></a>%BR%%BR% 1 Once connected to the DSN, click the associated <b>Link objects</b> to get a list of available objects (tables, views, stored procedures). %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb03.png"><img src="%ATTACHURLPATH%/VirtLinkSyb03.png" style="wikiautogen" width="600px" alt="VirtLinkSyb03.png" /></a>%BR%%BR% 1 Locate and select the desired objects. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb04.png"><img src="%ATTACHURLPATH%/VirtLinkSyb04.png" style="wikiautogen" width="600px" alt="VirtLinkSyb04.png" /></a>%BR%%BR% * You can use the Catalog and Schema drop-down selectors and the table name test-entry box to construct a filter to shorten the visible list. * For this example, we'll choose the key tables from the Sybase sample <b>pubs2.dbo</b> schema -- <b><code><nowiki>au_pix</nowiki></code>, <code><nowiki>authors</nowiki></code>, <code><nowiki>discounts</nowiki></code>, <code><nowiki>publishers</nowiki></code>, <code><nowiki>roysched</nowiki></code>, <code><nowiki>sales</nowiki></code>, <code><nowiki>salesdetail</nowiki></code>, <code><nowiki>stores</nowiki></code>, <code><nowiki>titleauthor</nowiki></code>, <code><nowiki>titles</nowiki></code></b>. * When all desired objects are selected, click the <b>Link...</b> button. 1 Virtuoso will interrogate the remote data source to learn about primary keys, and present you with a default linkage setup. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb05.png"><img src="%ATTACHURLPATH%/VirtLinkSyb05.png" style="wikiautogen" width="600px" alt="VirtLinkSyb05.png" /></a>%BR%%BR% 1 You can adjust the Virtuoso catalog, schema/owner, and object identifiers to suit your goals. The <b>Set To All</b> button can be used to speed the process. In this example, we'll put all linked objects into the <b><code>sybase12</code></b> catalog, and the <b><code>pubs2</code></b> schema. We'll leave the object identifiers unchanged. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb06.png"><img src="%ATTACHURLPATH%/VirtLinkSyb06.png" style="wikiautogen" width="600px" alt="VirtLinkSyb06.png" /></a>%BR%%BR% * Sometimes a primary key is not reported properly, or you want to use a different key, either simple or compound. Click <b>Edit</b> next to the primary key you want to change, and select the columns that Virtuoso should use for the purpose -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb07.png"><img src="%ATTACHURLPATH%/VirtLinkSyb07.png" style="wikiautogen" width="600px" alt="VirtLinkSyb07.png" /></a>%BR%%BR% 1 When all are set as desired, click the <b>Link</b> button to link the objects into Virtuoso. <i>Virtuoso may take some time to complete this step,</i> depending on network infrastructure, DBMS load, etc. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb07a.png"><img src="%ATTACHURLPATH%/VirtLinkSyb07a.png" style="wikiautogen" width="600px" alt="VirtLinkSyb07a.png" /></a>%BR%%BR% 1 The Link process will complete by listing the linked objects in the <b>Databases</b> -> <b>External Data Source</b> -> <b>External Linked Objects</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb08.png"><img src="%ATTACHURLPATH%/VirtLinkSyb08.png" style="wikiautogen" width="600px" alt="VirtLinkSyb08.png" /></a>%BR%%BR% ---++ Confirmation and Testing ---+++ Working with External Linked Objects (Tables, Views, and Stored Procedures) 1 Linked object are shown in the <b>Databases</b> -> <b>External Data Source</b> -> <b>External Linked Objects</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb08.png"><img src="%ATTACHURLPATH%/VirtLinkSyb08.png" style="wikiautogen" width="600px" alt="VirtLinkSyb08.png" /></a>%BR%%BR% 1 Clicking the hyperlinked <b>Local Name</b> of the <b>External Linked Objects</b> will load the Virtuoso <b>Interactive SQL</b> (iSQL) HTTP interface (in a new browser tab or window) with a default <b><code>SELECT *</code><b> SQL query. For instance, clicking on <b><code>sybase12.pubs2.authors</code></b> brings -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb09.png"><img src="%ATTACHURLPATH%/VirtLinkSyb09.png" style="wikiautogen" width="600px" alt="VirtLinkSyb09.png" /></a>%BR%%BR% 1 Click the <b>Execute</b> button to run the query. Virtuoso will retrieve the results from the remote table. <i><b>Note:</b> By default, iSQL will "<b>Show no more than 100 rows </b>." You can change this value as desired.</i> %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb10.png"><img src="%ATTACHURLPATH%/VirtLinkSyb10.png" style="wikiautogen" width="600px" alt="VirtLinkSyb10.png" /></a>%BR%%BR% ---+++ Working with SQL Database Objects (Tables, Views, and Stored Procedures) 1 Linked objects are also visible through the <b>Database</b> -> <b>SQL Database Object</b> tab, just as if they were local Virtuoso data. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb11.png"><img src="%ATTACHURLPATH%/VirtLinkSyb11.png" style="wikiautogen" width="600px" alt="VirtLinkSyb11.png" /></a>%BR%%BR% 1 Simply drill down to the Catalog you set while linking -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb12.png"><img src="%ATTACHURLPATH%/VirtLinkSyb12.png" style="wikiautogen" width="600px" alt="VirtLinkSyb12.png" /></a>%BR%%BR% 1 As you might expect, clicking on any of the <b>Action</b> links will reveal the table definition, indexes, triggers, constraints, or privileges. For example, clicking <b>Definition</b> for <b><code>informix.stores.orders</code></b> -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkSyb13.png"><img src="%ATTACHURLPATH%/VirtLinkSyb13.png" style="wikiautogen" width="600px" alt="VirtLinkSyb13.png" /></a>%BR%%BR% ---++ Related * [[VOSSQL2RDF][Mapping SQL Data to Linked Data Views]] * [[VirtSybaseEntityFrameworkUsage][Using Microsoft Entity Frameworks to Access Sybase Schema Objects (Tables, Views, and Stored Procedures) with Virtuoso]] CategoryDocumentation CategoryVirtuoso CategoryDotNET CategoryEntityFrameworks CategoryWebSite

sioc:id

3a6ffa17fb19fcec7e7de78f11005d21

sioc:link

n2:VirtSybaseLinkingObjects

sioc:has_container

n7:ODS

n19:has_services

n18:item

atom:title

VirtSybaseLinkingObjects

sioc:links_to

n11:VOSSQL2RDF n2:CategoryVirtuoso n11:VirtSybaseEntityFrameworkUsage n2:CategoryDocumentation n2:CategoryWebSite n11:CategoryEntityFrameworks n11:CategoryDotNET

atom:source

n7:ODS

atom:author

n26:this

atom:published

2017-06-13T06:04:03Z

atom:updated

2017-06-29T07:34:37Z

sioc:topic

n7:ODS

Subject Item

n27:this

sioc:creator_of

n2:VirtSybaseLinkingObjects