DBMS > Microsoft SQL Server vs. Postgres-XL vs. PouchDB vs. Riak KV vs. TempoIQ

System Properties Comparison Microsoft SQL Server vs. Postgres-XL vs. PouchDB vs. Riak KV vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Microsofts flagship relational DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

JavaScript DBMS with an API inspired by CouchDB

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

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

www.postgres-xl.org

pouchdb.com

tempoiq.com (offline)

Technical documentation

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

www.postgres-xl.org/documentation

pouchdb.com/guides

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Microsoft

Apache Software Foundation

OpenSource, formerly Basho Technologies

TempoIQ

Initial release

1989

2014

since 2012, originally named StormDB

2012

2009

2012

Current release

SQL Server 2022, November 2022

10 R1, October 2018

7.1.1, June 2019

3.2.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Mozilla public license

Open Source

Apache version 2, commercial enterprise edition

commercial

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++

JavaScript

Erlang

Server operating systems

Linux
Windows

Linux
macOS

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X

Data scheme

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

via views

restricted

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

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

user defined functions

View functions in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

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

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

yes, using Riak Security

simple authentication-based access control

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.