DBMS > Apache Drill vs. Cubrid vs. Lovefield vs. Microsoft SQL Server vs. PostGIS

System Properties Comparison Apache Drill vs. Cubrid vs. Lovefield vs. Microsoft SQL Server vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Embeddable relational database for web apps written in pure JavaScript

Microsofts flagship relational DBMS

Spatial extension of PostgreSQL

Primary database model

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

drill.apache.org

cubrid.com (korean)
cubrid.org (english)

google.github.io/lovefield

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

postgis.net

Technical documentation

drill.apache.org/docs

cubrid.org/manuals

github.com/google/lovefield/blob/master/docs/spec_index.md

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

postgis.net/documentation

Developer

Apache Software Foundation

CUBRID Corporation, CUBRID Foundation

Google

Microsoft

Initial release

2012

2008

2014

1989

2005

Current release

1.20.3, January 2023

11.0, January 2021

2.1.12, February 2017

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

GPL v2.0

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

JavaScript

C++

Server operating systems

Linux
OS X
Windows

Linux
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

Data scheme

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

via JavaScript builder pattern

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

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

Supported programming languages

C++

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

JavaScript

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

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

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

user defined functions

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.