DBMS > Google BigQuery vs. H2GIS vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere

System Properties Comparison Google BigQuery vs. H2GIS vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Spatial extension of H2

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Relational DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

cloud.google.com/bigquery

www.h2gis.org

azure.microsoft.com/services/cosmos-db

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

Technical documentation

cloud.google.com/bigquery/docs

www.h2gis.org/docs/home

learn.microsoft.com/azure/cosmos-db

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Google

CNRS

Microsoft

SAP

formerly Sybase

Initial release

2010

2013

2014

1992

Current release

17, July 2015

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

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.

Implementation language

Java

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

based on H2

JavaScript

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

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

yes

Implicit feature of the cloud service

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (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.

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

based on H2

Access rights can be defined down to the item level

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.