DBMS > Drizzle vs. Kingbase vs. Microsoft SQL Server vs. Splunk

System Properties Comparison Drizzle vs. Kingbase vs. Microsoft SQL Server vs. Splunk

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.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Microsofts flagship relational DBMS

Analytics Platform for Big Data

Primary database model

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.kingbase.com.cn

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

www.splunk.com

Technical documentation

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

docs.splunk.com/Documentation/Splunk

Developer

Drizzle project, originally started by Brian Aker

BeiJing KINGBASE Information technologies inc.

Microsoft

Splunk Inc.

Initial release

2008

1999

1989

2003

Current release

7.2.4, September 2012

V8.0, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

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

C and Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

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

Standard with numerous extensions

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

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

HTTP REST

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.