DBMS > Microsoft Azure SQL Database vs. Snowflake vs. Stardog vs. Warp 10

System Properties Comparison Microsoft Azure SQL Database vs. Snowflake vs. Stardog vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Graph DBMS
RDF store

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

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

www.snowflake.com

www.stardog.com

www.warp10.io

Technical documentation

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

docs.snowflake.net/manuals/index.html

docs.stardog.com

www.warp10.io/content/02_Getting_started

Developer

Microsoft

Snowflake Computing Inc.

Stardog-Union

SenX

Initial release

2010

2014

2010

2015

Current release

V12

7.3.0, May 2020

License

Commercial or Open Source

commercial

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

Open Source

Apache License 2.0

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

Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

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

schema-free and OWL/RDFS-schema support

schema-free

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

ADO.NET
JDBC
ODBC

CLI Client
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

HTTP API
Jupyter
WebSocket

Supported programming languages

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

JavaScript (Node.js)
Python

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

yes

WarpScript

Triggers

yes

similar concept for controling cloud resources

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes

Multi-source replication in HA-Cluster

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of 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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.