DBMS > Google BigQuery vs. Microsoft Azure Table Storage vs. Percona Server for MySQL vs. Qdrant vs. SAP SQL Anywhere

System Properties Comparison Google BigQuery vs. Microsoft Azure Table Storage vs. Percona Server for MySQL vs. Qdrant vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A Wide Column Store for rapid development using massive semi-structured datasets

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

cloud.google.com/bigquery

azure.microsoft.com/en-us/services/storage/tables

www.percona.com/software/mysql-database/percona-server

github.com/qdrant/qdrant
qdrant.tech

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

Technical documentation

cloud.google.com/bigquery/docs

www.percona.com/downloads/Percona-Server-LATEST

qdrant.tech/documentation

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Google

Microsoft

Percona

Qdrant

SAP

formerly Sybase

Initial release

2010

2012

2008

2021

1992

Current release

8.0.36-28, 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache Version 2.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

C and C++

Rust

Server operating systems

hosted

Linux

Docker
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication
XtraDB Cluster

Collection-level replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable 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

optimistic locking

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.

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

Key-based authentication

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.