DBMS > Microsoft Azure SQL Database vs. Microsoft SQL Server vs. NSDb vs. OrigoDB vs. RisingWave

System Properties Comparison Microsoft Azure SQL Database vs. Microsoft SQL Server vs. NSDb vs. OrigoDB vs. RisingWave

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Relational 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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.58
Rank	#242	Overall
	#111	Relational DBMS

Website

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

www.microsoft.com/en-us/sql-server

nsdb.io

origodb.com

www.risingwave.com/database

Technical documentation

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

learn.microsoft.com/en-US/sql/sql-server

nsdb.io/Architecture

origodb.com/docs

docs.risingwave.com/docs/current/intro

Developer

Microsoft

Robert Friberg et al

RisingWave Labs

Initial release

2010

1989

2017

2009

under the name LiveDB

2022

Current release

V12

SQL Server 2022, November 2022

1.2, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

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

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java, Scala

Rust

Server operating systems

hosted

Linux
Windows

Linux
macOS

Linux
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

Standard SQL-types and JSON

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

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

JDBC
PostgreSQL wire protocol

Supported programming languages

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
Scala

.Net

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Transact SQL

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

UDFs in Python or Java

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes, but depending on the SQL-Server Edition

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

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

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

Using Apache Lucene

yes

Write ahead log

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

Role based authorization

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.