DBMS > Google BigQuery vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB vs. Oracle Rdb vs. Sadas Engine

System Properties Comparison Google BigQuery vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB vs. Oracle Rdb vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used in-process key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

cloud.google.com/bigquery

azure.microsoft.com/en-us/products/azure-sql/database

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

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

www.sadasengine.com

Technical documentation

cloud.google.com/bigquery/docs

docs.microsoft.com/en-us/azure/azure-sql

docs.oracle.com/cd/E17076_05/html/index.html

www.oracle.com/database/technologies/related/rdb-doc.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Google

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle, originally developed by Digital Equipment Corporation (DEC)

SADAS s.r.l.

Initial release

2010

1994

1984

2006

Current release

V12

18.1.40, May 2020

7.4.1.1, 2021

8.0

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

free trial version available

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

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

HP Open VMS

AIX
Linux
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, 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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, on a single node

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.

yes

managed by 'Learn by Usage'

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

Access rights for users, groups and roles 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.