DBMS > Adabas vs. Microsoft Access vs. SiriDB vs. Snowflake vs. TempoIQ

System Properties Comparison Adabas vs. Microsoft Access vs. SiriDB vs. Snowflake vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

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

Open Source Time Series DBMS

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

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

Primary database model

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

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

siridb.com

www.snowflake.com

tempoiq.com (offline)

Technical documentation

developer.microsoft.com/en-us/access

docs.siridb.com

docs.snowflake.net/manuals/index.html

Developer

Software AG

Microsoft

Cesbit

Snowflake Computing Inc.

TempoIQ

Initial release

1971

1992

2017

2014

2012

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

MIT License

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

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

Not a real database server, but making use of DLLs

Linux

hosted

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

Numeric data

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

yes

with add-on product Adabas SQL Gateway

yes

but not compliant to any SQL standard

yes

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

ADO.NET
DAO
ODBC
OLE DB

HTTP API

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

Natural

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

in Natural

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

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

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

simple rights management via user accounts

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

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.