DBMS > Brytlyt vs. Kinetica vs. LMDB vs. Microsoft SQL Server vs. mSQL

System Properties Comparison Brytlyt vs. Kinetica vs. LMDB vs. Microsoft SQL Server vs. mSQL

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

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

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Website

brytlyt.io

www.kinetica.com

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

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

hughestech.com.au/products/msql

Technical documentation

docs.brytlyt.io

docs.kinetica.com

www.lmdb.tech/doc

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

Developer

Brytlyt

Kinetica

Symas

Microsoft

Hughes Technologies

Initial release

2016

2012

2011

1989

1994

Current release

5.0, August 2023

7.1, August 2021

0.9.32, January 2024

SQL Server 2022, November 2022

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

commercial

restricted free version is available

commercial

free licenses can be provided

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.

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

C, C++

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
Unix
Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

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

SQL-like DML and DDL statements

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C++
Java
JavaScript (Node.js)
Python

.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

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions

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

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

none

Foreign keys

Referential integrity

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

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.