DBMS > EsgynDB vs. SAP HANA vs. searchxml vs. SQream DB

System Properties Comparison EsgynDB vs. SAP HANA vs. searchxml vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

DBMS for structured and unstructured content wrapped with an application server

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

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	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.esgyn.cn

www.sap.com/products/hana.html

www.searchxml.net/category/products

sqream.com

Technical documentation

help.sap.com/hana

www.searchxml.net/support/handouts

docs.sqream.com

Developer

Esgyn

SAP

informationpartners gmbh

SQream Technologies

Initial release

2015

2010

2015

2017

Current release

2.0 SPS07 (April 4, 2023), April 2023

1.0

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

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

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux

Appliance or cloud-service

Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

.Net
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C++

most other programming languages supported via APIs

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

yes

on the application server

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

multiple readers, single writer

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

fine grained access rights according to SQL-standard

yes

Domain, group and role-based access control at the document level and for application services

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.