DBMS > Apache Drill vs. GeoSpock vs. Google BigQuery vs. Microsoft Access vs. Postgres-XL

System Properties Comparison Apache Drill vs. GeoSpock vs. Google BigQuery vs. Microsoft Access vs. Postgres-XL

Editorial information provided by DB-Engines

Name

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

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

drill.apache.org

geospock.com

cloud.google.com/bigquery

www.microsoft.com/en-us/microsoft-365/access

www.postgres-xl.org

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

www.postgres-xl.org/documentation

Developer

Apache Software Foundation

GeoSpock

Google

Microsoft

Initial release

2012

2010

1992

2014

since 2012, originally named StormDB

Current release

1.20.3, January 2023

2.0, September 2019

1902 (16.0.11328.20222), March 2019

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Bundled with Microsoft Office

Open Source

Mozilla public license

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

C++

Server operating systems

Linux
OS X
Windows

hosted

Windows

Not a real database server, but making use of DLLs

Linux
macOS

Data scheme

schema-free

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

XML type, but no XML query functionality

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

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

Supported programming languages

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

but no files for transaction logging

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per table

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

Google Cloud Identity & Access Management (IAM)

a simple user-level security was built in till version Access 2003

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.