DBMS > Heroic vs. Microsoft SQL Server vs. Riak TS vs. Teradata Aster

System Properties Comparison Heroic vs. Microsoft SQL Server vs. Riak TS vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Microsofts flagship relational DBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Platform for big data analytics on multistructured data sources and types

Primary database model

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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

github.com/spotify/heroic

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

Technical documentation

spotify.github.io/heroic

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

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Spotify

Microsoft

Open Source, formerly Basho Technologies

Teradata

Initial release

2014

1989

2015

2005

Current release

SQL Server 2022, November 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

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

Erlang

Server operating systems

Linux
Windows

Linux
OS X

Linux

Data scheme

schema-free

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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

in Aster File Store

Secondary indexes

yes

via Elasticsearch

yes

restricted

yes

SQL

Support of SQL

yes

yes, limited

yes

APIs and other access methods

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

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

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

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

Erlang

R packages

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

selectable replication factor

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

In-memory capabilities

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

yes

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.