DBMS > IBM Db2 warehouse vs. Oracle NoSQL vs. SAP HANA vs. Splunk

System Properties Comparison IBM Db2 warehouse vs. Oracle NoSQL vs. SAP HANA vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-based data warehousing service

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

In-memory, column based data store. Available as appliance or cloud service

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

www.ibm.com/products/db2/warehouse

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

IBM

Oracle

SAP

Splunk Inc.

Initial release

2014

2011

2010

2003

Current release

24.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

Linux
Solaris SPARC/x86

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

Splunk Search Processing Language for search commands

APIs and other access methods

.NET Client API
JDBC
ODBC
OLE DB

RESTful HTTP API

JDBC
ODBC

HTTP REST

Supported programming languages

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

PL/SQL, SQL PL

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

yes

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

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.