DBMS > EXASOL vs. Microsoft SQL Server vs. OrigoDB vs. RavenDB

System Properties Comparison EXASOL vs. Microsoft SQL Server vs. OrigoDB vs. RavenDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Microsofts flagship relational DBMS

A fully ACID in-memory object graph database

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Document 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	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

www.exasol.com

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

origodb.com

ravendb.net

Technical documentation

www.exasol.com/resources

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

origodb.com/docs

ravendb.net/docs

Developer

Exasol

Microsoft

Robert Friberg et al

Hibernating Rhinos

Initial release

2000

1989

2009

under the name LiveDB

2010

Current release

SQL Server 2022, November 2022

5.4, July 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license 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++

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

SQL

Support of SQL

yes

SQL-like query language (RQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

.NET Client API
HTTP API
LINQ

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

Supported programming languages

Java
Lua
Python
R

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

.Net

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

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

depending on model

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

Role based authorization

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.