DBMS > Apache Drill vs. Interbase vs. Microsoft Access vs. Snowflake vs. SwayDB

System Properties Comparison Apache Drill vs. Interbase vs. Microsoft Access vs. Snowflake vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

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

Light-weight proven RDBMS

originally from Borland

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

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

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.61
Rank	#72	Overall
	#39	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

drill.apache.org

www.embarcadero.com/products/interbase

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

www.snowflake.com

swaydb.simer.au

Technical documentation

drill.apache.org/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Embarcadero

Microsoft

Snowflake Computing Inc.

Simer Plaha

Initial release

2012

1984

1992

2014

2018

Current release

1.20.3, January 2023

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Bundled with Microsoft Office

commercial

Open Source

GNU Affero GPL V3.0

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

C++

Scala

Server operating systems

Linux
OS X
Windows

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

yes

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

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

C++

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

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

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

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

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

none

yes

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

ACID

but no files for transaction logging

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

Depending on the underlying data source

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.

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

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

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.