DBMS > Atos Standard Common Repository vs. SAP IQ vs. Snowflake vs. Splunk vs. STSdb

System Properties Comparison Atos Standard Common Repository vs. SAP IQ vs. Snowflake vs. Splunk vs. STSdb

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Columnar RDBMS optimized for Big Data analytics

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

column-oriented

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

Score	2.56
Rank	#106	Overall
	#52	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

www.splunk.com

github.com/STSSoft/STSdb4

Technical documentation

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

SAP, formerly Sybase

Snowflake Computing Inc.

Splunk Inc.

STS Soft SC

Initial release

2016

1994

2014

2003

2011

Current release

1703

16.1 SPS04, April 2019

4.0.8, September 2015

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

Open Source

GPLv2, commercial license available

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

Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

optional

yes

primitive types and user defined types (classes)

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

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP REST

.NET Client API

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

SAP/Sybase Replication Server

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

LDAP bind authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.