DBMS > Amazon DocumentDB vs. Microsoft SQL Server vs. Tibero vs. Trafodion

System Properties Comparison Amazon DocumentDB vs. Microsoft SQL Server vs. Tibero vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Microsofts flagship relational DBMS

A secure RDBMS, designed for easy portability from Oracle

Transactional SQL-on-Hadoop DBMS

Primary database model

Document 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	1.91
Rank	#132	Overall
	#24	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

aws.amazon.com/documentdb

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

us.tmaxsoft.com/products/tibero

trafodion.apache.org

Technical documentation

aws.amazon.com/documentdb/resources

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

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

trafodion.apache.org/documentation.html

Developer

Microsoft

TmaxSoft

Apache Software Foundation, originally developed by HP

Initial release

2019

1989

2003

2014

Current release

SQL Server 2022, November 2022

6, April 2015

2.3.0, February 2019

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache 2.0

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

C and Assembler

C++, Java

Server operating systems

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

proprietary protocol using JSON (MongoDB compatible)

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

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

Persistent Stored Procedure (PSM)

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

horizontal partitioning

by range, hash, list or composite

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

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

planned for next version

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.