W3C home > Mailing lists > Public > semantic-web@w3.org > November 2016

Re: Storing RDF in a relational database

From: Bernadette Hyland <bhyland@3roundstones.com>
Date: Thu, 3 Nov 2016 00:24:08 +1000
Message-Id: <9EB3234C-6AAD-47B9-9B6A-04B7D5EF608C@3roundstones.com>
Cc: "semantic-web@w3.org" <semantic-web@w3.org>
To: "Li, Ai-jun" <Ai-jun.Li@morganstanley.com>
Hi Ai-jun,
Not sure that storing RDF triples in a relational database is novel, at least not in 2016. And 300M isn’t a big number in the world of graph databases. For example, we’re working with a linked data repository, PubChem with 99B triples, and linking it to a subset of environmental linked open data. Point is, graph databases are a useful tool for specific jobs, just like RDBMS’s are great for other jobs. 

More importantly, getting triples out in a speedy manner, using a standard query language, and building a nice UI, is the part many people in the linked data community have spent 10+ years getting right.

Just my 2 cents.

Cheers,

Bernadette Hyland
CEO, 3 Round Stones, Inc.



> On Nov 2, 2016, at 04:11, Li, Ai-jun <Ai-jun.Li@morganstanley.com> wrote:
> 
> 
> I came across a very old request for comments for storing RDF data in relational database (http://infolab.stanford.edu/~melnik/rdf/db.html <http://infolab.stanford.edu/~melnik/rdf/db.html>). I was unable to find any newer discussion on this. We had implemented a very innovative way of storing linked graph data in Sybase many years ago and the system is still being used today. The system is storing the equivalent of over 300 million triples and is scalable for much more. We’d be happy to share our approach if this is something the community is still interested in (will need to get the firm’s approval, obviously).
>  
> Thanks,
> Ai-jun Li   
> Morgan Stanley | Enterprise Infrastructure   
> 1 New York Plaza, 16th Floor | New York, NY  10004   
> Phone: +1 646 536-0765   
> Ai-jun.Li@morganstanley.com <mailto:Ai-jun.Li@morganstanley.com>   
>    
> 
> 
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers <http://www.morganstanley.com/disclaimers>  If you cannot access these links, please notify us by reply message and we will send the contents to you. By communicating with Morgan Stanley you consent to the foregoing and to the voice recording of conversations with personnel of Morgan Stanley.
Received on Wednesday, 2 November 2016 14:24:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 November 2016 14:24:45 UTC