DBMS > Graphite vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere vs. Snowflake vs. Splunk

System Properties Comparison Graphite vs. Microsoft Azure SQL Database vs. SAP SQL Anywhere vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Database as a Service offering with high compatibility to Microsoft SQL Server

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Analytics Platform for Big Data

Primary database model

Time Series DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

github.com/graphite-project/graphite-web

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

www.splunk.com

Technical documentation

graphite.readthedocs.io

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Chris Davis

Microsoft

SAP

formerly Sybase

Snowflake Computing Inc.

Splunk Inc.

Initial release

2006

2010

1992

2014

2003

Current release

V12

17, July 2015

License

Commercial or Open Source

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

Python

C++

Server operating systems

Linux
Unix

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

Numeric data only

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

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

HTTP API
Sockets

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

JavaScript (Node.js)
Python

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL

yes, in C/C++, Java, .Net or Perl

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

Source-replica replication

Database mirroring

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

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

locking

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

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.