DBMS > Apache Drill vs. Microsoft SQL Server vs. OpenQM vs. SWC-DB vs. Transbase

System Properties Comparison Apache Drill vs. Microsoft SQL Server vs. OpenQM vs. SWC-DB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Microsofts flagship relational DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

A high performance, scalable Wide Column DBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.33
Rank	#286	Overall
	#10	Multivalue DBMS

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

drill.apache.org

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

drill.apache.org/docs

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

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation

Microsoft

Rocket Software, originally Martin Phillips

Alex Kashirin

Transaction Software GmbH

Initial release

2012

1989

1993

2020

1987

Current release

1.20.3, January 2023

SQL Server 2022, November 2022

3.4-12

0.5, April 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license available

Open Source

GPL V3

commercial

free development license

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

Server operating systems

Linux
OS X
Windows

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

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

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C++

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

.Net
Basic
C
Java
Objective C
PHP
Python

C++

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.