DBMS > GeoSpock vs. Google BigQuery vs. Interbase vs. Microsoft Access vs. OpenQM

System Properties Comparison GeoSpock vs. Google BigQuery vs. Interbase vs. Microsoft Access vs. OpenQM

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

Large scale data warehouse service with append-only tables

Light-weight proven RDBMS

originally from Borland

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.)

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Relational DBMS

Multivalue DBMS

Secondary database models

Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Website

geospock.com

cloud.google.com/bigquery

www.embarcadero.com/products/interbase

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

cloud.google.com/bigquery/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

Developer

GeoSpock

Google

Embarcadero

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2010

1984

1992

1993

Current release

2.0, September 2019

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

3.4-12

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

GPLv2, extended commercial license available

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

hosted

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

with some exceptions

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.

export as XML data possible

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

none

yes

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

Since BigQuery is designed for querying data

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

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.

yes

User concepts

Access control

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)

fine grained access rights according to SQL-standard

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

Access rights can be defined down to the item level

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.