DBMS > Apache Drill vs. BigObject vs. Microsoft Access vs. SQLite

System Properties Comparison Apache Drill vs. BigObject vs. Microsoft Access vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for real-time computations and queries

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.13
Rank	#342	Overall
	#150	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

bigobject.io

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

www.sqlite.org

Technical documentation

drill.apache.org/docs

docs.bigobject.io

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

Developer

Apache Software Foundation

BigObject, Inc.

Microsoft

Dwayne Richard Hipp

Initial release

2012

2015

1992

2000

Current release

1.20.3, January 2023

1902 (16.0.11328.20222), March 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free community edition available

commercial

Bundled with Microsoft Office

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux
OS X
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

schema-free

yes

dynamic column types

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

fluentd
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

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

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

Server-side scripts

Stored procedures

user defined functions

Lua

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

yes

via file-system locks

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

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

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.