DBMS > Apache Drill vs. Google BigQuery vs. GridGain vs. SAP SQL Anywhere

System Properties Comparison Apache Drill vs. Google BigQuery vs. GridGain vs. SAP SQL Anywhere

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

Large scale data warehouse service with append-only tables

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Relational DBMS

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Website

drill.apache.org

cloud.google.com/bigquery

www.gridgain.com

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Google

GridGain Systems, Inc.

SAP

formerly Sybase

Initial release

2012

2010

2007

1992

Current release

1.20.3, January 2023

GridGain 8.5.1

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

commercial, open source

commercial

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, Python, REST, SQL

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris
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

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

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

Since BigQuery is designed for querying data

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control
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.