DBMS > AlaSQL vs. Apache Drill vs. Ingres vs. Interbase vs. SAP HANA

System Properties Comparison AlaSQL vs. Apache Drill vs. Ingres vs. Interbase vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Well established RDBMS

Light-weight proven RDBMS

originally from Borland

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

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

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

alasql.org

drill.apache.org

www.actian.com/databases/ingres

www.embarcadero.com/products/interbase

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

docs.actian.com/ingres

docs.embarcadero.com/products/interbase

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Actian Corporation

Embarcadero

SAP

Initial release

2014

2012

1974

originally developed at University Berkely in early 1970s

1984

2010

Current release

1.20.3, January 2023

12.0, July 2024

InterBase 2020, December 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Android
iOS
Linux
OS X
Windows

Appliance or cloud-service

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.

but tools for importing/exporting data from/to XML-files available

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

JavaScript

C++

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Ingres Replicator

Interbase Change Views

yes

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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.

yes

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

yes

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.