DBMS > LMDB vs. Microsoft Access vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

System Properties Comparison LMDB vs. Microsoft Access vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

A high performant, light-weight, embedded key-value database 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.)

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Key-value store

Relational DBMS

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

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.symas.com/symas-embedded-database-lmdb

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

www.oracle.com/database/technologies/related/rdb.html

www.snowflake.com

Technical documentation

www.lmdb.tech/doc

developer.microsoft.com/en-us/access

www.oracle.com/database/technologies/related/rdb-doc.html

docs.snowflake.net/manuals/index.html

Developer

Symas

Microsoft

Oracle, originally developed by Digital Equipment Corporation (DEC)

Snowflake Computing Inc.

Teradata

Initial release

2011

1992

1984

2014

2005

Current release

0.9.32, January 2024

1902 (16.0.11328.20222), March 2019

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

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

C++

Server operating systems

Linux
Unix
Windows

Windows

Not a real database server, but making use of DLLs

HP Open VMS

hosted

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

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

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

R packages

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

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

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

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.