DBMS > Google BigQuery vs. Microsoft Azure SQL Database vs. Realm vs. Stardog

System Properties Comparison Google BigQuery vs. Microsoft Azure SQL Database vs. Realm vs. Stardog

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

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

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Relational DBMS

Document store

Graph DBMS
RDF store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

cloud.google.com/bigquery

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

realm.io

www.stardog.com

Technical documentation

cloud.google.com/bigquery/docs

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

realm.io/docs

docs.stardog.com

Developer

Google

Microsoft

Realm, acquired by MongoDB in May 2019

Stardog-Union

Initial release

2010

2014

2010

Current release

V12

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
Java

with Android only
Objective-C
React Native
Swift

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

runs within the applications so server-side scripts are unnecessary

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Change Listeners

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

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

In-Memory realm

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

yes

Access rights for users and roles

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.