DBMS > Google BigQuery vs. Graph Engine vs. Microsoft Azure Synapse Analytics vs. Snowflake vs. SQLite

System Properties Comparison Google BigQuery vs. Graph Engine vs. Microsoft Azure Synapse Analytics vs. Snowflake vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Cloud-based data warehousing service for structured and semi-structured data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/bigquery

www.graphengine.io

azure.microsoft.com/services/synapse-analytics

www.snowflake.com

www.sqlite.org

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.microsoft.com/azure/synapse-analytics

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

Developer

Google

Microsoft

Snowflake Computing Inc.

Dwayne Richard Hipp

Initial release

2010

2016

2014

2000

Current release

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

Public Domain

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

.NET and C

C++

Server operating systems

hosted

.NET

hosted

server-less

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C#
Java
PHP

JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Transact SQL

user defined functions

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding, horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

via file-system locks

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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)

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.