DBMS > Google BigQuery vs. Microsoft Azure SQL Database vs. PostGIS vs. Sequoiadb vs. TimescaleDB

System Properties Comparison Google BigQuery vs. Microsoft Azure SQL Database vs. PostGIS vs. Sequoiadb vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Spatial DBMS

Document store
Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

cloud.google.com/bigquery

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

postgis.net

www.sequoiadb.com

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

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

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.timescale.com

Developer

Google

Microsoft

Sequoiadb Ltd.

Timescale

Initial release

2010

2005

2013

2017

Current release

V12

3.4.2, February 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.0

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

C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C++
Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

user defined functions

JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes

based on PostgreSQL

Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Document is locked during a transaction

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.

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

simple password-based access control

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.