DBMS > Drizzle vs. IBM Cloudant vs. Kyligence Enterprise vs. Microsoft SQL Server

System Properties Comparison Drizzle vs. IBM Cloudant vs. Kyligence Enterprise vs. Microsoft SQL Server

Please select another system to include it in the comparison.

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.

Database as a Service offering based on Apache CouchDB

A distributed analytics engine for big data, built on top of Apache Kylin

Microsofts flagship relational DBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

www.ibm.com/products/cloudant

kyligence.io/kyligence-enterprise

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

Technical documentation

cloud.ibm.com/docs/Cloudant

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

Developer

Drizzle project, originally started by Brian Aker

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Kyligence, Inc.

Microsoft

Initial release

2008

2010

2016

1989

Current release

7.2.4, September 2012

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GNU GPL

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.

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

Erlang

Java

C++

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux

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

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

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

Supported programming languages

C
C++
Java
PHP

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

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

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

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.