DBMS > GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. ToroDB vs. Transbase

System Properties Comparison GeoMesa vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. ToroDB vs. Transbase

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A resource-optimized, high-performance, universally applicable RDBMS

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.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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.geomesa.org

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

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

github.com/torodb/server

www.transaction.de/en/products/transbase.html

Technical documentation

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

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

help.sap.com/docs/SAP_SQL_Anywhere

www.transaction.de/en/products/transbase/features.html

Developer

CCRi and others

Microsoft

SAP

formerly Sybase

8Kdata

Transaction Software GmbH

Initial release

2014

1989

1992

2016

1987

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

Open Source

AGPL-V3

commercial

free development license

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

C++

Java

C and C++

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

APIs and other access methods

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

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

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

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

fine grained access rights according to SQL-standard

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