DBMS > Apache Drill vs. Heroic vs. SAP Advantage Database Server vs. Snowflake vs. Splunk

System Properties Comparison Apache Drill vs. Heroic vs. SAP Advantage Database Server vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

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

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

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

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

Search engine

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

drill.apache.org

github.com/spotify/heroic

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

www.snowflake.com

www.splunk.com

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Spotify

Sybase, SAP

Snowflake Computing Inc.

Splunk Inc.

Initial release

2012

2014

1993

2014

2003

Current release

1.20.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

C++

Delphi
Perl
PHP

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

Multi-source replication

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

caching of (temporary) tables can be configured

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

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.