DBMS > Microsoft SQL Server vs. Oracle NoSQL vs. RavenDB vs. TerarkDB

System Properties Comparison Microsoft SQL Server vs. Oracle NoSQL vs. RavenDB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Open Source Operational and Transactional Enterprise NoSQL Document Database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Document store

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	2.96
Rank	#103	Overall
	#18	Document stores
	#17	Key-value stores
	#52	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

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

www.oracle.com/database/nosql/technologies/nosql

ravendb.net

github.com/bytedance/terarkdb

Technical documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

ravendb.net/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Microsoft

Oracle

Hibernating Rhinos

ByteDance, originally Terark

Initial release

1989

2011

2010

2016

Current release

SQL Server 2022, November 2022

23.3, December 2023

5.4, July 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

AGPL version 3, commercial license available

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C++

Server operating systems

Linux
Windows

Linux
Solaris SPARC/x86

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

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

SQL-like DML and DDL statements

SQL-like query language (RQL)

APIs and other access methods

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

RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

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

C++
Java

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID, Cluster-wide transaction available

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

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

Authorization levels configured per client per database

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.