DBMS > Kdb vs. Machbase Neo vs. Microsoft SQL Server vs. Sphinx vs. XTDB

System Properties Comparison Kdb vs. Machbase Neo vs. Microsoft SQL Server vs. Sphinx vs. XTDB

Editorial information provided by DB-Engines

Name

Description

High performance Time Series DBMS

TimeSeries DBMS for AIoT and BigData

Microsofts flagship relational DBMS

Open source search engine for searching in data from different sources, e.g. relational databases

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Time Series DBMS
Vector DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

kx.com

machbase.com

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

sphinxsearch.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

code.kx.com

machbase.com/dbms

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

sphinxsearch.com/docs

www.xtdb.com/docs

Developer

Kx Systems, a division of First Derivatives plc

Machbase

Microsoft

Sphinx Technologies Inc.

Juxt Ltd.

Initial release

2000

kdb was released 2000, kdb+ in 2003

2013

1989

2001

2019

Current release

3.6, May 2018

V8.0, August 2023

SQL Server 2022, November 2022

3.5.1, February 2023

1.19, September 2021

License

Commercial or Open Source

commercial

free 32-bit version

commercial

free test version available

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Open Source

MIT License

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

Clojure

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

table attribute 'grouped'

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (q)

SQL-like query language

yes

SQL-like query language (SphinxQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

Proprietary protocol

HTTP REST
JDBC

Supported programming languages

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes, but depending on the SQL-Server Edition

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

The original contents of fields are not stored in the Sphinx index.

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

rights management via user accounts

simple password-based access control

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.