DBMS > Heroic vs. IRONdb vs. LevelDB vs. Microsoft SQL Server vs. SAP Advantage Database Server

System Properties Comparison Heroic vs. IRONdb vs. LevelDB vs. Microsoft SQL Server vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Microsofts flagship relational DBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/spotify/heroic

www.circonus.com/solutions/time-series-database/

github.com/google/leveldb

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

www.sap.com/products/advantage-database-server.html

Technical documentation

spotify.github.io/heroic

docs.circonus.com/irondb/category/getting-started

github.com/google/leveldb/blob/main/doc/index.md

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

Developer

Spotify

Circonus LLC.

Google

Microsoft

Sybase, SAP

Initial release

2014

2017

2011

1989

1993

Current release

V0.10.20, January 2018

1.23, February 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

commercial

restricted free version is available

commercial

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

C++

Server operating systems

Linux

Illumos
Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

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

HTTP API

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes, in Lua

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

none

yes, but depending on the SQL-Server Edition

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

yes

caching of (temporary) tables can be configured

User concepts

Access control

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.