DBMS > Elasticsearch vs. Microsoft SQL Server vs. Splunk vs. Trafodion

System Properties Comparison Elasticsearch vs. Microsoft SQL Server vs. Splunk vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Microsofts flagship relational DBMS

Analytics Platform for Big Data

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

www.elastic.co/elasticsearch

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

www.splunk.com

trafodion.apache.org

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

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

docs.splunk.com/Documentation/Splunk

trafodion.apache.org/documentation.html

Developer

Elastic

Microsoft

Splunk Inc.

Apache Software Foundation, originally developed by HP

Initial release

2010

1989

2003

2014

Current release

8.6, January 2023

SQL Server 2022, November 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Elastic License

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

Apache 2.0

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

C++, Java

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

HTTP REST

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C#
Java
JavaScript
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

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

yes

Java Stored Procedures

Triggers

yes

by using the 'percolation' feature

yes

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

Multi-source replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Eventual Consistency

Immediate 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

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.

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.