DBMS > Amazon Neptune vs. Atos Standard Common Repository vs. EsgynDB vs. Microsoft SQL Server vs. Netezza

System Properties Comparison Amazon Neptune vs. Atos Standard Common Repository vs. EsgynDB vs. Microsoft SQL Server vs. Netezza

Editorial information provided by DB-Engines

Name

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

Description

Fast, reliable graph database built for the cloud

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Microsofts flagship relational DBMS

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Website

aws.amazon.com/neptune

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

www.esgyn.cn

www.microsoft.com/en-us/sql-server

www.ibm.com/products/netezza

Technical documentation

aws.amazon.com/neptune/developer-resources

learn.microsoft.com/en-US/sql/sql-server

Developer

Amazon

Atos Convergence Creators

Esgyn

Microsoft

IBM

Initial release

2017

2016

2015

1989

2000

Current release

1703

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++, Java

C++

Server operating systems

hosted

Linux

Linux
Windows

Linux

included in appliance

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

LDAP

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC
OLE DB

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages with LDAP bindings

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

Java Stored Procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

Multi-source replication between multi datacenters

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.