DBMS > Heroic vs. Microsoft Access vs. Microsoft SQL Server vs. Sqrrl

System Properties Comparison Heroic vs. Microsoft Access vs. Microsoft SQL Server vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/spotify/heroic

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

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

sqrrl.com

Technical documentation

spotify.github.io/heroic

developer.microsoft.com/en-us/access

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

Developer

Spotify

Microsoft

Amazon

originally Sqrrl Data, Inc.

Initial release

2014

1992

1989

2012

Current release

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

commercial

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

Java

C++

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

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)

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

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

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes, but depending on the SQL-Server Edition

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

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

fine grained access rights according to SQL-standard

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.