DBMS > Apache Drill vs. GridGain vs. IBM Db2 warehouse vs. SAP IQ vs. SQLite

System Properties Comparison Apache Drill vs. GridGain vs. IBM Db2 warehouse vs. SAP IQ vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

GridGain is an in-memory computing platform, built on Apache Ignite

Cloud-based data warehousing service

Columnar RDBMS optimized for Big Data analytics

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

column-oriented

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.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

www.gridgain.com

www.ibm.com/products/db2/warehouse

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.sqlite.org

Technical documentation

drill.apache.org/docs

www.gridgain.com/docs/index.html

help.sap.com/docs/SAP_IQ

www.sqlite.org/docs.html

Developer

Apache Software Foundation

GridGain Systems, Inc.

IBM

SAP, formerly Sybase

Dwayne Richard Hipp

Initial release

2012

2007

2014

1994

2000

Current release

1.20.3, January 2023

GridGain 8.5.1

16.1 SPS04, April 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Public Domain

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.

Implementation language

Java, C++, .Net

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

C#
C++
Java
PHP
Python
Ruby
Scala

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
C++
Java
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

PL/SQL, SQL PL

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

SAP/Sybase Replication Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Hadoop integration

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

via file-system locks

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

Security Hooks for custom implementations

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.