DBMS > Atos Standard Common Repository vs. BaseX vs. Dolt vs. Microsoft SQL Server

System Properties Comparison Atos Standard Common Repository vs. BaseX vs. Dolt vs. Microsoft SQL Server

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

A MySQL compatible DBMS with Git-like versioning of data and schema

Microsofts flagship relational DBMS

Primary database model

Document store
Key-value store

Native XML DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

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

basex.org

github.com/dolthub/dolt
www.dolthub.com

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

Technical documentation

docs.basex.org

docs.dolthub.com

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

Developer

Atos Convergence Creators

BaseX GmbH

DoltHub Inc

Microsoft

Initial release

2016

2007

2018

1989

Current release

1703

10.7, August 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache Version 2.0

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

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Windows

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

XQuery supports types

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

LDAP

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

CLI Client
HTTP REST

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

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

currently in alpha release

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

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

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

multiple readers, single writer

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

User concepts

Access control

LDAP bind authentication

Users with fine-grained authorization concept on 4 levels

Only one user is configurable, and must be specified in the config file at startup

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.