DBMS > Google BigQuery vs. MySQL vs. searchxml vs. UniData,UniVerse

System Properties Comparison Google BigQuery vs. MySQL vs. searchxml vs. UniData,UniVerse

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

Widely used open source RDBMS

DBMS for structured and unstructured content wrapped with an application server

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Multivalue DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	2.25
Rank	#112	Overall
	#2	Multivalue DBMS

Website

cloud.google.com/bigquery

www.mysql.com

www.searchxml.net/category/products

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

cloud.google.com/bigquery/docs

dev.mysql.com/doc

www.searchxml.net/support/handouts

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Rocket Software

Initial release

2010

1995

2015

1985

Current release

9.0.0, July 2024

1.0

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

most other programming languages supported via APIs

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

yes

on the application server

yes

Triggers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

multiple readers, single writer

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

Access rights according to SQL-standard and operating system based

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.