DBMS > GeoMesa vs. Ingres vs. Microsoft SQL Server vs. TDSQL for MySQL

System Properties Comparison GeoMesa vs. Ingres vs. Microsoft SQL Server vs. TDSQL for MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Well established RDBMS

Microsofts flagship relational DBMS

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Website

www.geomesa.org

www.actian.com/databases/ingres

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

www.tencentcloud.com/products/dcdb

Technical documentation

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

docs.actian.com/ingres

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

www.tencentcloud.com/document/product/1042

Developer

CCRi and others

Actian Corporation

Microsoft

Tencent

Initial release

2014

1974

originally developed at University Berkely in early 1970s

1989

2013

Current release

4.0.5, February 2024

11.2, May 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Scala

C++

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Windows

hosted

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

JDBC
ODBC

Supported programming languages

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

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

Ingres Star to access multiple databases simultaneously

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

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Ingres Replicator

yes, but depending on the SQL-Server Edition

Multi-source replication
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

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

MVCC

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

Users with fine-grained authorization concept

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.