DBMS > IBM Db2 Event Store vs. Microsoft SQL Server vs. Snowflake vs. Splunk vs. Tarantool

System Properties Comparison IBM Db2 Event Store vs. Microsoft SQL Server vs. Snowflake vs. Splunk vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

Microsofts flagship relational DBMS

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

Analytics Platform for Big Data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Event Store
Time Series DBMS

Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.ibm.com/products/db2-event-store

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

www.snowflake.com

www.splunk.com

www.tarantool.io

Technical documentation

www.ibm.com/docs/en/db2-event-store

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

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

www.tarantool.io/en/doc

Developer

IBM

Microsoft

Snowflake Computing Inc.

Splunk Inc.

Initial release

2017

1989

2014

2003

2008

Current release

2.0

SQL Server 2022, November 2022

2.10.0, May 2022

License

Commercial or Open Source

commercial

free developer edition available

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

C++

C and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

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

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

through the embedded Spark runtime

yes

Splunk Search Processing Language for search commands

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

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

CLI Client
JDBC
ODBC

HTTP REST

Open binary protocol

Supported programming languages

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

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

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

user defined functions

yes

Lua, C and SQL stored procedures

Triggers

yes

similar concept for controling cloud resources

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

yes, but depending on the SQL-Server Edition

yes

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

yes, cooperative multitasking

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.