DBMS > Google BigQuery vs. Riak KV vs. SAP SQL Anywhere vs. TimesTen

System Properties Comparison Google BigQuery vs. Riak KV vs. SAP SQL Anywhere vs. TimesTen

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

Distributed, fault tolerant key-value store

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

cloud.google.com/bigquery

www.sap.com/products/technology-platform/sql-anywhere.html

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

Technical documentation

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/docs/SAP_SQL_Anywhere

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

Developer

Google

OpenSource, formerly Basho Technologies

SAP

formerly Sybase

Oracle

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

Initial release

2010

2009

1992

1998

Current release

3.2.0, December 2022

17, July 2015

Release 22.1

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows

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

Data scheme

yes

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

ADO.NET
HTTP API
JDBC
ODBC

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Erlang

yes, in C/C++, Java, .Net or Perl

PL/SQL

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Database mirroring

Multi-source replication
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

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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)

yes, using Riak Security

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.