DBMS > Amazon DocumentDB vs. Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. OpenQM

System Properties Comparison Amazon DocumentDB vs. Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. OpenQM

Editorial information provided by DB-Engines

Name

Description

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

Light-weight proven RDBMS

originally from Borland

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

aws.amazon.com/documentdb

www.embarcadero.com/products/interbase

azure.microsoft.com/en-us/services/storage/tables

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

aws.amazon.com/documentdb/resources

docs.embarcadero.com/products/interbase

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

Developer

Embarcadero

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2019

1984

2012

1989

1993

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

3.4-12

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPLv2, extended 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

C++

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

hosted

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

with some exceptions

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

ADO.NET
JDBC
ODBC

RESTful HTTP API

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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

Implicit feature of the cloud service

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

Interbase Change Views

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.