Mulgara. OpenRDF. Parliament. Jena. SDB - persistent triple stores using relational databases SDB uses an SQL database for the storage and query of RDF data. Many databases are supported, both Open Source and proprietary. An SDB store can be accessed and managed with the provided command line scripts and via the Jena API. Use of SDB for new applications is not recommended. This component is "maintenance only". TDB is faster, more scalable and better supported than SDB. Status As of June 2013 the Jena developers agreed to treat SDB as being only maintanined where possible. The developers intend to continue releasing SDB alongside other Jena components but it is not actively developed. SDB may be revived as a fully supported component if members of the community come forward to develop it. Documentation Downloads SDB is distributed from the Apache Jena project.
Subversion SDB subversion repository at Apache. Support Support and questions Details Database Notes List of databases supported Notes: LargeTripleStores. This page is for references to signed quotes of deployments of large triples stores rather than predictions of what some software might scale to. Table of Contents: AllegroGraph (1+Trillion) Franz announced at the June 2011 Semtech conference a load and query of 310 Billion triples as part of a joint project with Intel. In August 2011, with the help of Stillwater SC and Intel we achieved the industry's first load and query of 1 Trillion RDF Triples. Total load was 1,009,690,381,946 triples in just over 338 hours for an average rate of 829,556 triples per second. The driving force has been Amdocs and their AIDA platform.
We currently load LUBM 8000 in just over 36 minutes. Franz is in late-stage development on a clustered version of AllegroGraph that will push storage into trillions of triples. Note 1: AllegroGraph provides dynamic reasoning and DOES NOT require materialization. Stardog (50B) OpenLink Virtuoso v6.1 - 15.4B+ explicit; uncounted virtual/inferred Benchmarks data sources. 4store.