DBMS > Sadas Engine vs. SAP SQL Anywhere vs. Splunk vs. SQL.JS vs. SQLite

System Properties Comparison Sadas Engine vs. SAP SQL Anywhere vs. Splunk vs. SQL.JS vs. SQLite

Editorial information provided by DB-Engines

Name

Description

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

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

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.sadasengine.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

sql.js.org

www.sqlite.org

Technical documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

SADAS s.r.l.

SAP

formerly Sybase

Splunk Inc.

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2006

1992

2003

2012

2000

Current release

8.0

17, July 2015

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

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

C++

JavaScript

Server operating systems

AIX
Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
Proprietary protocol

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C#
C++
Groovy
Java
PHP
Python

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Database mirroring

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

Access rights for users and roles

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.