DBMS > Apache Impala vs. Microsoft SQL Server vs. Splice Machine vs. Warp 10

System Properties Comparison Apache Impala vs. Microsoft SQL Server vs. Splice Machine vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Microsofts flagship relational DBMS

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

impala.apache.org

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

splicemachine.com

www.warp10.io

Technical documentation

impala.apache.org/impala-docs.html

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

splicemachine.com/how-it-works

www.warp10.io/content/02_Getting_started

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Microsoft

Splice Machine

SenX

Initial release

2013

1989

2014

2015

Current release

4.1.0, June 2022

SQL Server 2022, November 2022

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

AGPL 3.0, commercial license available

Open Source

Apache License 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

C++

Java

Server operating systems

Linux

Linux
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

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

JDBC
Native Spark Datasource
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

yes

Java

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.