DBMS > Apache Drill vs. Heroic vs. InfinityDB vs. Microsoft SQL Server

System Properties Comparison Apache Drill vs. Heroic vs. InfinityDB vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A Java embedded Key-Value Store which extends the Java Map interface

Microsofts flagship relational DBMS

Primary database model

Document store
Relational DBMS

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

drill.apache.org

github.com/spotify/heroic

boilerbay.com

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

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

boilerbay.com/infinitydb/manual

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

Developer

Apache Software Foundation

Spotify

Boiler Bay Inc.

Microsoft

Initial release

2012

2014

2002

1989

Current release

1.20.3, January 2023

4.0

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

restricted free version is available

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++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
Windows

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

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

via Elasticsearch

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

Supported programming languages

C++

Java

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

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.