DBMS > Google BigQuery vs. Riak TS vs. SAP Adaptive Server vs. TigerGraph

System Properties Comparison Google BigQuery vs. Riak TS vs. SAP Adaptive Server vs. TigerGraph

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

cloud.google.com/bigquery

www.sap.com/products/technology-platform/sybase-ase.html

www.tigergraph.com

Technical documentation

cloud.google.com/bigquery/docs

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

help.sap.com/docs/SAP_ASE

docs.tigergraph.com

Developer

Google

Open Source, formerly Basho Technologies

SAP, Sybase

Initial release

2010

2015

1987

2017

Current release

3.0.0, September 2022

16.0

License

Commercial or Open Source

commercial

Open Source

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

C and C++

C++

Server operating systems

hosted

Linux
OS X

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

yes, limited

yes

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

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++
Cobol
Java
Java
Perl
PHP
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Erlang

Java and Transact-SQL

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

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

Foreign keys

Referential integrity

links between datasets can be stored

yes

Relationships in graphs

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

In-memory capabilities

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

User concepts

Access control

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

Role-based access control

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.