DBMS > Google BigQuery vs. H2 vs. JaguarDB vs. Microsoft Azure SQL Database vs. Valentina Server

System Properties Comparison Google BigQuery vs. H2 vs. JaguarDB vs. Microsoft Azure SQL Database vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Performant, highly scalable DBMS for AI and IoT applications

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

Object-relational database and reports server

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	0.18
Rank	#329	Overall
	#144	Relational DBMS

Website

cloud.google.com/bigquery

www.h2database.com

www.jaguardb.com

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

www.valentina-db.net

Technical documentation

cloud.google.com/bigquery/docs

www.h2database.com/html/main.html

www.jaguardb.com/support.html

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

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Thomas Mueller

DataJaguar, Inc.

Microsoft

Paradigma Software

Initial release

2010

2005

2015

2010

1999

Current release

2.2.220, July 2023

3.3 July 2023

V12

5.7.5

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

GPL V3.0

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

Java

C++

the server part. Clients available in other languages

C++

Server operating systems

hosted

All OS with a Java VM

Linux

hosted

Linux
OS X
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC

ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java Stored Procedures and User-Defined Functions

Transact SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

Multi-source replication

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

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

rights management via user accounts

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.