DBMS > KeyDB vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Sequoiadb

System Properties Comparison KeyDB vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

Wide column store

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	0.42
Rank	#263	Overall
	#41	Document stores
	#121	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/en-us/services/storage/tables

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

www.sequoiadb.com

Technical documentation

docs.keydb.dev

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

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

EQ Alpha Technology Ltd.

Microsoft

Sequoiadb Ltd.

Initial release

2019

2012

1989

2013

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

BSD-3

commercial

restricted free version is available

Open Source

Server: AGPL; Client: Apache V2

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

Server operating systems

Linux

hosted

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

oid, date, timestamp, binary, regex

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API

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

proprietary protocol using JSON

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

Lua

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

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

optimistic locking

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

simple password-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.