DBMS > Google BigQuery vs. RavenDB vs. SAP Adaptive Server vs. Spark SQL

System Properties Comparison Google BigQuery vs. RavenDB vs. SAP Adaptive Server vs. Spark SQL

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

cloud.google.com/bigquery

ravendb.net

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

spark.apache.org/sql

Technical documentation

cloud.google.com/bigquery/docs

ravendb.net/docs

help.sap.com/docs/SAP_ASE

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Google

Hibernating Rhinos

SAP, Sybase

Apache Software Foundation

Initial release

2010

1987

2014

Current release

5.4, July 2022

16.0

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

commercial

Open Source

Apache 2.0

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 and C++

Scala

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux
OS X
Windows

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

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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, Cluster-wide transaction available

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)

Authorization levels configured per client per database

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.