DBMS > Brytlyt vs. LMDB vs. Microsoft SQL Server vs. SAP Advantage Database Server vs. VoltDB

System Properties Comparison Brytlyt vs. LMDB vs. Microsoft SQL Server vs. SAP Advantage Database Server vs. VoltDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

A high performant, light-weight, embedded key-value database library

Microsofts flagship relational DBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key-value 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.38
Rank	#279	Overall
	#126	Relational DBMS

Score	2.33
Rank	#118	Overall
	#21	Key-value stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

brytlyt.io

www.symas.com/symas-embedded-database-lmdb

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

www.sap.com/products/advantage-database-server.html

www.voltdb.com

Technical documentation

docs.brytlyt.io

www.lmdb.tech/doc

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

docs.voltdb.com

Developer

Brytlyt

Symas

Microsoft

Sybase, SAP

VoltDB Inc.

Initial release

2016

2011

1989

1993

2010

Current release

5.0, August 2023

0.9.32, January 2024

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

commercial

restricted free version is available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++ and CUDA

C++

Java, C++

Server operating systems

Linux
OS X
Windows

Linux
Unix
Windows

Linux
Windows

Linux
OS X

for development

Data scheme

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

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

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

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

Delphi
Perl
PHP

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

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

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes, but depending on the SQL-Server Edition

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

caching of (temporary) tables can be configured

User concepts

Access control

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.