DBMS > Apache Impala vs. EsgynDB vs. Microsoft Azure SQL Database vs. SAP HANA

System Properties Comparison Apache Impala vs. EsgynDB vs. Microsoft Azure SQL Database vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

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

Primary database model

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

impala.apache.org

www.esgyn.cn

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

www.sap.com/products/hana.html

Technical documentation

impala.apache.org/impala-docs.html

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

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Esgyn

Microsoft

SAP

Initial release

2013

2015

2010

Current release

4.1.0, June 2022

V12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

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

C++

C++, Java

C++

Server operating systems

Linux

hosted

Appliance or cloud-service

Data scheme

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Java Stored Procedures

Transact SQL

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication between multi datacenters

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

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

yes

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.