DBMS > Dolt vs. OrigoDB vs. SAP HANA vs. Sqrrl

System Properties Comparison Dolt vs. OrigoDB vs. SAP HANA 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

A MySQL compatible DBMS with Git-like versioning of data and schema

A fully ACID in-memory object graph database

In-memory, column based data store. Available as appliance or cloud service

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

origodb.com

www.sap.com/products/hana.html

sqrrl.com

Technical documentation

docs.dolthub.com

origodb.com/docs

help.sap.com/hana

Developer

DoltHub Inc

Robert Friberg et al

SAP

Amazon

originally Sqrrl Data, Inc.

Initial release

2018

2009

under the name LiveDB

2010

2012

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux
macOS
Windows

Linux
Windows

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
HTTP REST

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

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

currently in alpha release

yes

SQLScript, R

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

yes

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

Immediate Consistency

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

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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 one user is configurable, and must be specified in the config file at startup

Role based authorization

yes

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.