DBMS > Drizzle vs. JaguarDB vs. Kinetica vs. Microsoft Azure Table Storage vs. Microsoft SQL Server

System Properties Comparison Drizzle vs. JaguarDB vs. Kinetica vs. Microsoft Azure Table Storage vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Performant, highly scalable DBMS for AI and IoT applications

Fully vectorized database across both GPUs and CPUs

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Wide column 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.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.jaguardb.com

www.kinetica.com

azure.microsoft.com/en-us/services/storage/tables

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

Technical documentation

www.jaguardb.com/support.html

docs.kinetica.com

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

Developer

Drizzle project, originally started by Brian Aker

DataJaguar, Inc.

Kinetica

Microsoft

Initial release

2008

2015

2012

1989

Current release

7.2.4, September 2012

3.3 July 2023

7.1, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL V3.0

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

the server part. Clients available in other languages

C, C++

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

hosted

Linux
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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

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

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

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

Triggers

hooks for callbacks inside the server can be used.

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

Implicit feature of the cloud service

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

rights management via user accounts

Access rights for users and roles on table level

Access rights based on private key authentication or shared access signatures

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.