DBMS > Heroic vs. Microsoft Access vs. Microsoft SQL Server vs. SiriDB vs. XTDB

System Properties Comparison Heroic vs. Microsoft Access vs. Microsoft SQL Server vs. SiriDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Microsofts flagship relational DBMS

Open Source Time Series DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

github.com/spotify/heroic

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

www.microsoft.com/en-us/sql-server

siridb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

spotify.github.io/heroic

developer.microsoft.com/en-us/access

learn.microsoft.com/en-US/sql/sql-server

docs.siridb.com

www.xtdb.com/docs

Developer

Spotify

Microsoft

Cesbit

Juxt Ltd.

Initial release

2014

1992

1989

2017

2019

Current release

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

MIT License

Open Source

MIT License

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Clojure

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data

yes, extensible-data-notation format

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

via Elasticsearch

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP API

HTTP REST
JDBC

Supported programming languages

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Clojure
Java

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes, but depending on the SQL-Server Edition

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

simple rights management via user accounts

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.