DBMS > LevelDB vs. Microsoft SQL Server vs. Riak TS vs. Teradata

System Properties Comparison LevelDB vs. Microsoft SQL Server vs. Riak TS vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Microsofts flagship relational DBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

github.com/google/leveldb

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

www.teradata.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

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

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

docs.teradata.com

Developer

Google

Microsoft

Open Source, formerly Basho Technologies

Teradata

Initial release

2011

1989

2015

1984

Current release

1.23, February 2021

SQL Server 2022, November 2022

3.0.0, September 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

BSD

commercial

restricted free version is available

Open Source

commercial

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

Erlang

Server operating systems

Illumos
Linux
OS X
Windows

Linux
Windows

Linux
OS X

hosted
Linux

Data scheme

schema-free

yes

schema-free

yes

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

Secondary indexes

yes

restricted

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

yes, limited

yes

SQL 2016 + extensions

APIs and other access methods

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

HTTP API
Native Erlang Interface

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

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
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

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

Erlang

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

selectable replication factor

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

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

with automatic compression on writes

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

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.