DBMS > BigObject vs. Google BigQuery vs. Microsoft Access vs. TimesTen

System Properties Comparison BigObject vs. Google BigQuery vs. Microsoft Access vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

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

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

bigobject.io

cloud.google.com/bigquery

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

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.bigobject.io

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

BigObject, Inc.

Google

Microsoft

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2015

2010

1992

1998

Current release

1902 (16.0.11328.20222), March 2019

Release 22.1

License

Commercial or Open Source

commercial

free community edition available

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

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Windows

Not a real database server, but making use of DLLs

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

PL/SQL

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by means of logfiles and checkpoints

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)

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.