DBMS > Kdb vs. Microsoft SQL Server vs. Oracle NoSQL

System Properties Comparison Kdb vs. Microsoft SQL Server vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Time Series DBMS
Vector DBMS

Relational DBMS

Document store
Key-value store
Relational 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	8.28
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	903.83
Rank	#3	Overall
	#3	Relational DBMS

Score	4.02
Rank	#93	Overall
	#16	Document stores
	#14	Key-value stores
	#49	Relational DBMS

Website

kx.com

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

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

code.kx.com

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Kx Systems, a division of First Derivatives plc

Microsoft

Oracle

Initial release

2000

kdb was released 2000, kdb+ in 2003

1989

2011

Current release

3.6, May 2018

SQL Server 2022, November 2022

23.1, May 2023

License

Commercial or Open Source

commercial

free 32-bit version

commercial

restricted free version is available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
Solaris SPARC/x86

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

SQL-like query language (q)

yes

SQL-like DML and DDL statements

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

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

RESTful HTTP API

Supported programming languages

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

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

C
C#
Go
Java
JavaScript (Node.js)
Python

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

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

rights management via user accounts

fine grained access rights according to SQL-standard

Access rights for users and roles

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.