DBMS > Apache Drill vs. Geode vs. Microsoft SQL Server vs. Newts

System Properties Comparison Apache Drill vs. Geode vs. Microsoft SQL Server vs. Newts

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Microsofts flagship relational DBMS

Time Series DBMS based on Cassandra

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial 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	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Website

drill.apache.org

geode.apache.org

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

opennms.github.io/newts

Technical documentation

drill.apache.org/docs

geode.apache.org/docs

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

github.com/OpenNMS/newts/wiki

Developer

Apache Software Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

OpenNMS Group

Initial release

2012

2002

1989

2014

Current release

1.20.3, January 2023

1.1, February 2017

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

Apache 2.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

Java

C++

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

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

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

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

HTTP REST
Java API

Supported programming languages

C++

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Java

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, but depending on the SQL-Server Edition

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

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

Access rights per client and object definable

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.