DBMS > GeoSpock vs. Microsoft Azure SQL Database vs. Microsoft SQL Server vs. VoltDB

System Properties Comparison GeoSpock vs. Microsoft Azure SQL Database vs. Microsoft SQL Server vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Spatial and temporal data processing engine for extreme data scale

Database as a Service offering with high compatibility to Microsoft SQL Server

Microsofts flagship relational DBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

geospock.com

azure.microsoft.com/en-us/products/azure-sql/database

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

www.voltdb.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

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

docs.voltdb.com

Developer

GeoSpock

Microsoft

VoltDB Inc.

Initial release

2010

1989

2010

Current release

2.0, September 2019

V12

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, Javascript

C++

Java, C++

Server operating systems

hosted

Linux
Windows

Linux
OS X

for development

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

only a subset of SQL 99

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

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

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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 can be defined per table

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.