DBMS > Microsoft Azure SQL Database vs. SAP SQL Anywhere vs. Splunk vs. SQLite vs. TerminusDB

System Properties Comparison Microsoft Azure SQL Database vs. SAP SQL Anywhere vs. Splunk vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

azure.microsoft.com/en-us/products/azure-sql/database

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

www.splunk.com

www.sqlite.org

terminusdb.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Microsoft

SAP

formerly Sybase

Splunk Inc.

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2010

1992

2003

2000

2018

Current release

V12

17, July 2015

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

Open Source

GPL V3

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++

Prolog, Rust

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C#
Java
JavaScript
PHP
Python
Ruby

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

JavaScript
Python

Server-side scripts

Stored procedures

Transact SQL

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Source-replica replication

Database mirroring

Multi-source replication

none

Journaling Streams

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

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

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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