DBMS > AlaSQL vs. Microsoft Access vs. RDFox vs. Snowflake

System Properties Comparison AlaSQL vs. Microsoft Access vs. RDFox vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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.)

High performance knowledge graph and semantic reasoning engine

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Relational DBMS

Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

alasql.org

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

www.oxfordsemantic.tech

www.snowflake.com

Technical documentation

github.com/AlaSQL/alasql

developer.microsoft.com/en-us/access

docs.oxfordsemantic.tech

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Microsoft

Oxford Semantic Technologies

Snowflake Computing Inc.

Initial release

2014

1992

2017

2014

Current release

1902 (16.0.11328.20222), March 2019

6.0, Septermber 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

Bundled with Microsoft Office

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

JavaScript

C++

Server operating systems

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

Windows

Not a real database server, but making use of DLLs

Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

RDF schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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

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

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API
SPARQL 1.1

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

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

C
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

replication via a shared file system

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

but no files for transaction logging

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

Roles, resources, and access types

Users with fine-grained authorization concept, user roles and pluggable authentication

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.