DBMS > Apache Drill vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. SQLite vs. Valentina Server

System Properties Comparison Apache Drill vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. SQLite vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Document store
Relational DBMS

Wide column store

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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

drill.apache.org

azure.microsoft.com/en-us/services/storage/tables

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

www.sqlite.org

www.valentina-db.net

Technical documentation

drill.apache.org/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Microsoft

SAP

formerly Sybase

Dwayne Richard Hipp

Paradigma Software

Initial release

2012

1992

2000

1999

Current release

1.20.3, January 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

5.7.5

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Public Domain

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

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

C++

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

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

optimistic locking

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

Access rights based on private key authentication or shared access signatures

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.