DBMS > Hive vs. Microsoft SQL Server vs. RDF4J vs. Solr

System Properties Comparison Hive vs. Microsoft SQL Server vs. RDF4J vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Microsofts flagship relational DBMS

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

RDF store

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	62.59
Rank	#18	Overall
	#12	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

hive.apache.org

www.microsoft.com/en-us/sql-server

rdf4j.org

solr.apache.org

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

learn.microsoft.com/en-US/sql/sql-server

rdf4j.org/documentation

solr.apache.org/resources.html

Developer

Apache Software Foundation

initially developed by Facebook

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Apache Software Foundation

Initial release

2012

1989

2004

2006

Current release

3.1.3, April 2022

SQL Server 2022, November 2022

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Java

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
OS X
Unix
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

RDF Schemas

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC
Thrift

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Java API
RESTful HTTP/JSON API

Supported programming languages

C++
Java
PHP
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Isolation support depends on the API used

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

yes

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.