DBMS > Dolt vs. FatDB vs. Microsoft SQL Server vs. Teradata Aster vs. TigerGraph

System Properties Comparison Dolt vs. FatDB vs. Microsoft SQL Server vs. Teradata Aster vs. TigerGraph

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Microsofts flagship relational DBMS

Platform for big data analytics on multistructured data sources and types

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Graph 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	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

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

www.tigergraph.com

Technical documentation

docs.dolthub.com

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

docs.tigergraph.com

Developer

DoltHub Inc

FatCloud

Microsoft

Teradata

Initial release

2018

2012

1989

2005

2017

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

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

C++

Server operating systems

Linux
macOS
Windows

Windows

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

SQL-like query language (GSQL)

APIs and other access methods

CLI Client
HTTP REST

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

ADO.NET
JDBC
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

via applications

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

R packages

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

yes, but depending on the SQL-Server Edition

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

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

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

Can implement custom security layer via applications

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.