DBMS > Drizzle vs. JaguarDB vs. Microsoft SQL Server vs. OrigoDB vs. TDSQL for MySQL

System Properties Comparison Drizzle vs. JaguarDB vs. Microsoft SQL Server vs. OrigoDB vs. TDSQL for MySQL

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

Microsofts flagship relational DBMS

A fully ACID in-memory object graph database

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Website

www.jaguardb.com

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

origodb.com

www.tencentcloud.com/products/dcdb

Technical documentation

www.jaguardb.com/support.html

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

origodb.com/docs

www.tencentcloud.com/document/product/1042

Developer

Drizzle project, originally started by Brian Aker

DataJaguar, Inc.

Microsoft

Robert Friberg et al

Tencent

Initial release

2008

2015

1989

2009

under the name LiveDB

2013

Current release

7.2.4, September 2012

3.3 July 2023

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

Open Source

commercial

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

Server operating systems

FreeBSD
Linux
OS X

Linux

Linux
Windows

hosted

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC

JDBC
ODBC

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

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

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

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

.Net

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

client side managed; servers are not synchronized

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes, but depending on the SQL-Server Edition

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

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

Write ahead log

yes

In-memory capabilities

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

rights management via user accounts

fine grained access rights according to SQL-standard

Role based authorization

Users with fine-grained authorization concept

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.