DBMS > Apache Drill vs. JaguarDB vs. SAP IQ vs. Snowflake vs. Trafodion

System Properties Comparison Apache Drill vs. JaguarDB vs. SAP IQ vs. Snowflake vs. Trafodion

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

Performant, highly scalable DBMS for AI and IoT applications

Columnar RDBMS optimized for Big Data analytics

Cloud-based data warehousing service for structured and semi-structured data

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

Key-value store
Vector 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	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

www.jaguardb.com

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

www.snowflake.com

trafodion.apache.org

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

DataJaguar, Inc.

SAP, formerly Sybase

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2012

2015

1994

2014

Current release

1.20.3, January 2023

3.3 July 2023

16.1 SPS04, April 2019

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

Open Source

Apache 2.0

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

C++

the server part. Clients available in other languages

C++, Java

Server operating systems

Linux
OS X
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

C++

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

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Java Stored Procedures

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

SAP/Sybase Replication Server

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

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

User concepts

Access control

Depending on the underlying data source

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.