DBMS > Apache Drill vs. JaguarDB vs. SAP SQL Anywhere vs. SQLite vs. Yanza

System Properties Comparison Apache Drill vs. JaguarDB vs. SAP SQL Anywhere vs. SQLite vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. 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

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

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Document store
Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Time Series 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	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

www.jaguardb.com

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

www.sqlite.org

yanza.com

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

Developer

Apache Software Foundation

DataJaguar, Inc.

SAP

formerly Sybase

Dwayne Richard Hipp

Yanza

Initial release

2012

2015

1992

2000

2015

Current release

1.20.3, January 2023

3.3 July 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Server operating systems

Linux
OS X
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

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

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

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

C++

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

Database mirroring

none

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

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

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

rights management via user accounts

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.