1 / 9

Enhancing Business Intelligence with SPARQL: Integrating SQL Workloads and RDF Data

Discover the potential of SPARQL for business intelligence in this insightful presentation by Orri Erling, Program Manager at Virtuoso. Explore how SPARQL can facilitate seamless integration and analysis across relational databases and RDF data sources. This document covers essential aspects like aggregation, nested queries, and expressions, alongside practical guidance for defining mappings and optimizing performance. Learn from use cases including OpenLink MIS and MusicBrainz, demonstrating the capabilities of SPARQL in handling dynamic and extensive datasets effectively.

cade
Download Presentation

Enhancing Business Intelligence with SPARQL: Integrating SQL Workloads and RDF Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPARQL for Business Intelligence • Orri Erling - Program Manager, Virtuoso © 2008 OpenLink Software, All rights reserved. 1

  2. For The Data Web to Deliver • Promise of limitless integration and analysis • Existing SQL workloads should naturally fall within SPARQL’s scope • Surfing and joining between relational data and RDF should be seamless © 2008 OpenLink Software, All rights reserved. 2

  3. What Is Missing? • Aggregation • Nested Queries • Expressions © 2008 OpenLink Software, All rights reserved. 3

  4. Mapped vs. Physical RDF • Predicates are unspecified • Combining lots off different data sources • Lots of A-box inference (SameAs, Transitivity) • Mapped is better, if: Physical is better, if: • Can push all to RDBMS - about 10x faster • Data is time-sensitive, frequently changing, very large © 2008 OpenLink Software, All rights reserved.

  5. When defining mappings... • Be careful when many tables make one entity - you may get lots of unions • Make explicit IRI scheme to limit pointless joining • Know what the mapper and SQL can and cannot optimize © 2008 OpenLink Software, All rights reserved. 5

  6. Some Present Work • Refining generated SQL • There is no reason why SPARQL mapped should not equal SQL in performance, when going to single DBMS © 2008 OpenLink Software, All rights reserved.

  7. Joining Between Mapped and Physical • Special SQL logic is needed when joining IRI IDs of physical quads with IRI strings of virtual triples • SameAs requires special attention © 2008 OpenLink Software, All rights reserved. 7

  8. Use Cases • OpenLink MIS • All accounts, CRM, products, emails, support cases have URIs • MusicBrainz • OpenLink Data Spaces • PHPbb, Mediawiki, Drupal, etc. © 2008 OpenLink Software, All rights reserved. 8

  9. OpenLink Software Thank You! http://virtuoso.openlinksw.com © 2008 OpenLink Software, All rights reserved.

More Related