DBMS > Microsoft Access vs. SAP HANA vs. SAP SQL Anywhere vs. SQL.JS vs. Yanza

System Properties Comparison Microsoft Access vs. SAP HANA vs. SAP SQL Anywhere vs. SQL.JS vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

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

Port of SQLite to JavaScript

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series 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	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

www.microsoft.com/en-us/microsoft-365/access

www.sap.com/products/hana.html

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

sql.js.org

yanza.com

Technical documentation

developer.microsoft.com/en-us/access

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

sql.js.org/documentation/index.html

Developer

Microsoft

SAP

formerly Sybase

Alon Zakai

enhancements implemented by others

Yanza

Initial release

1992

2010

1992

2012

2015

Current release

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based 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++

JavaScript

Server operating systems

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

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

Windows

Data scheme

yes

schema-free

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

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

JavaScript API

HTTP API

Supported programming languages

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

JavaScript

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

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

Triggers

yes

since Access 2010 using the ACE-engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

a simple user-level security was built in till version Access 2003

yes

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.