DBMS > Apache Drill vs. GridGain vs. Microsoft SQL Server vs. Trafodion

System Properties Comparison Apache Drill vs. GridGain vs. Microsoft SQL Server vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Microsofts flagship relational DBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

drill.apache.org

www.gridgain.com

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

trafodion.apache.org

Technical documentation

drill.apache.org/docs

www.gridgain.com/docs/index.html

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

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

GridGain Systems, Inc.

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2012

2007

1989

2014

Current release

1.20.3, January 2023

GridGain 8.5.1

SQL Server 2022, November 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java, C++, .Net

C++

C++, Java

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Linux
Windows

Linux

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

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

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

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

ADO.NET
JDBC
ODBC

Supported programming languages

C++

C#
C++
Java
PHP
Python
Ruby
Scala

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

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

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

Java Stored Procedures

Triggers

yes (cache interceptors and events)

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, but depending on the SQL-Server Edition

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

via user defined functions and HBase

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

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.