DBMS > Google BigQuery vs. HBase vs. Microsoft Access vs. OpenEdge

System Properties Comparison Google BigQuery vs. HBase vs. Microsoft Access vs. OpenEdge

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Application development environment with integrated database management system

Primary database model

Relational DBMS

Wide column store

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

cloud.google.com/bigquery

hbase.apache.org

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

www.progress.com/openedge

Technical documentation

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

developer.microsoft.com/en-us/access

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Progress Software Corporation

Initial release

2010

2008

1992

1984

Current release

2.3.4, January 2021

1902 (16.0.11328.20222), March 2019

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

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

C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Windows

Not a real database server, but making use of DLLs

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

close to SQL 92

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Coprocessors in Java

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

none

Sharding

none

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or 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

Single row ACID (across millions of columns)

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

Users and groups

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.