DBMS > Infobright vs. SAP SQL Anywhere vs. SQL.JS vs. SQLite vs. Yanza

System Properties Comparison Infobright vs. SAP SQL Anywhere vs. SQL.JS 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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

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

sql.js.org

www.sqlite.org

yanza.com

Technical documentation

help.sap.com/docs/SAP_SQL_Anywhere

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP

formerly Sybase

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Yanza

Initial release

2005

1992

2012

2000

2015

Current release

17, July 2015

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

JavaScript

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

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

server-less

Windows

Data scheme

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

JavaScript

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

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

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

via file-system locks

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.