DBMS > Atos Standard Common Repository vs. Kinetica vs. Netezza vs. Oracle

System Properties Comparison Atos Standard Common Repository vs. Kinetica vs. Netezza vs. Oracle

Please select another system to include it in the comparison.

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

Fully vectorized database across both GPUs and CPUs

Data warehouse and analytics appliance part of IBM PureSystems

Widely used RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Website

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

www.kinetica.com

www.ibm.com/products/netezza

www.oracle.com/database

Technical documentation

docs.kinetica.com

docs.oracle.com/en/database

Developer

Atos Convergence Creators

Kinetica

IBM

Oracle

Initial release

2016

2012

2000

1980

Current release

1703

7.1, August 2021

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

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

C and C++

Server operating systems

Linux

included in appliance

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

Schema and schema-less with LDAP views

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

optional

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

LDAP

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages with LDAP bindings

C++
Java
JavaScript (Node.js)
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate 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

isolation level can be parameterized

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

GPU vRAM or System RAM

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

LDAP bind authentication

Access rights for users and roles on table level

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

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.