DBMS > Apache Impala vs. Atos Standard Common Repository vs. Microsoft Azure AI Search vs. Microsoft SQL Server vs. TerminusDB

System Properties Comparison Apache Impala vs. Atos Standard Common Repository vs. Microsoft Azure AI Search vs. Microsoft SQL Server vs. TerminusDB

Editorial information provided by DB-Engines

Name

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

Description

Analytic DBMS for Hadoop

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

Search-as-a-service for web and mobile app development

Microsofts flagship relational DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Document store
Key-value store

Search engine

Relational DBMS

Graph DBMS

Secondary database models

Document store

Vector DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

impala.apache.org

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

azure.microsoft.com/en-us/services/search

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

terminusdb.com

Technical documentation

impala.apache.org/impala-docs.html

learn.microsoft.com/en-us/azure/search

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

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Atos Convergence Creators

Microsoft

DataChemist Ltd.

Initial release

2013

2016

2015

1989

2018

Current release

4.1.0, June 2022

1703

SQL Server 2022, November 2022

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

GPL V3

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

Java

C++

Prolog, Rust

Server operating systems

Linux

hosted

Linux
Windows

Linux

Data scheme

yes

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

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

LDAP

RESTful HTTP API

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C#
Java
JavaScript
Python

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Sharding

cell division

Sharding

Implicit feature of the cloud service

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

yes, but depending on the SQL-Server Edition

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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, groups and roles

based on Apache Sentry and Kerberos

LDAP bind authentication

yes

using Azure authentication

fine grained access rights according to SQL-standard

Role-based access control

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.