DBMS > Apache Impala vs. GeoSpock vs. Microsoft SQL Server vs. MonetDB vs. ToroDB

System Properties Comparison Apache Impala vs. GeoSpock vs. Microsoft SQL Server vs. MonetDB vs. ToroDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

Analytic DBMS for Hadoop

Spatial and temporal data processing engine for extreme data scale

Microsofts flagship relational DBMS

A relational database management system that stores data in columns

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

Primary database model

Relational DBMS

Document store

Secondary database models

Document store

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Website

impala.apache.org

geospock.com

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

www.monetdb.org

github.com/torodb/server

Technical documentation

impala.apache.org/impala-docs.html

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

www.monetdb.org/Documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

GeoSpock

Microsoft

MonetDB BV

8Kdata

Initial release

2013

1989

2004

2016

Current release

4.1.0, June 2022

2.0, September 2019

SQL Server 2022, November 2022

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

Mozilla Public License 2.0

Open Source

AGPL-V3

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

C++

Java, Javascript

C++

Java

Server operating systems

Linux

hosted

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

temporal, categorical

yes

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI SQL for query only (using Presto)

yes

SQL 2003 with some extensions

APIs and other access methods

JDBC
ODBC

JDBC

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

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

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 SQL, C, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

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

Sharding via remote tables

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

none

Source-replica replication available in experimental status

Source-replica replication

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

Eventual Consistency

Immediate Consistency

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.

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Access rights for users and roles

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.