DBMS > AnzoGraph DB vs. EsgynDB vs. GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere

System Properties Comparison AnzoGraph DB vs. EsgynDB vs. GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Microsofts flagship relational DBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.esgyn.cn

www.geomesa.org

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

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

www.geomesa.org/documentation/stable/user/index.html

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Cambridge Semantics

Esgyn

CCRi and others

Microsoft

SAP

formerly Sybase

Initial release

2018

2015

2014

1989

1992

Current release

2.3, January 2021

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

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

Scala

C++

Server operating systems

Linux

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

ADO.NET
JDBC
ODBC

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C++
Java
Python

All languages supporting JDBC/ODBC/ADO.Net

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

Java Stored Procedures

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

depending on storage layer

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication between multi datacenters

depending on storage layer

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.