DBMS > GeoSpock vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. Snowflake vs. SQLite

System Properties Comparison GeoSpock vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. Snowflake vs. SQLite

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

Cloud-based data warehousing service for structured and semi-structured data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

azure.microsoft.com/en-us/services/storage/tables

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

www.snowflake.com

www.sqlite.org

Technical documentation

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

Developer

GeoSpock

Microsoft

SAP

formerly Sybase

Snowflake Computing Inc.

Dwayne Richard Hipp

Initial release

2012

1992

2014

2000

Current release

2.0, September 2019

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

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.

Implementation language

Java, Javascript

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

server-less

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

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

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Implicit feature of the cloud service

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

Database mirroring

yes

none

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

Transaction concepts

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.