DBMS > GeoMesa vs. Hive vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. SQream DB

System Properties Comparison GeoMesa vs. Hive vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Microsofts flagship relational DBMS

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

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

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

www.geomesa.org

hive.apache.org

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

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

sqream.com

Technical documentation

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

cwiki.apache.org/confluence/display/Hive/Home

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

help.sap.com/docs/SAP_SQL_Anywhere

docs.sqream.com

Developer

CCRi and others

Apache Software Foundation

initially developed by Facebook

Microsoft

SAP

formerly Sybase

SQream Technologies

Initial release

2014

2012

1989

1992

2017

Current release

4.0.5, February 2024

3.1.3, April 2022

SQL Server 2022, November 2022

17, July 2015

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2

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

Scala

Java

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

All OS with a Java VM

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Thrift

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

ADO.NET
HTTP API
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

C++
Java
PHP
Python

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

C++
Java
JavaScript (Node.js)
Python

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, in C/C++, Java, .Net or Perl

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

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

none

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users, groups 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.