DBMS > Microsoft Access vs. Microsoft Azure Data Explorer vs. OrientDB vs. SQLite vs. TempoIQ

System Properties Comparison Microsoft Access vs. Microsoft Azure Data Explorer vs. OrientDB vs. SQLite vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed 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.)

Fully managed big data interactive analytics platform

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

column oriented

Document store
Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

azure.microsoft.com/services/data-explorer

orientdb.org

www.sqlite.org

tempoiq.com (offline)

Technical documentation

developer.microsoft.com/en-us/access

docs.microsoft.com/en-us/azure/data-explorer

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

Microsoft

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

TempoIQ

Initial release

1992

2019

2010

2000

2012

Current release

1902 (16.0.11328.20222), March 2019

cloud service with continuous releases

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache version 2

Open Source

Public Domain

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

C++

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

yes

not rigid because of 'dynamic typing' concept.

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

Kusto Query Language (KQL), SQL subset

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Yes, possible languages: KQL, Python, R

Java, Javascript

Triggers

yes

since Access 2010 using the ACE-engine

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

via file-system locks

yes

Durability

Support for making data persistent

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

Azure Active Directory Authentication

Access rights for users and roles; record level security configurable

simple authentication-based access control

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.