DBMS > Axibase vs. Graph Engine vs. Microsoft SQL Server vs. TerminusDB

System Properties Comparison Axibase vs. Graph Engine vs. Microsoft SQL Server vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Microsofts flagship relational DBMS

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

Primary database model

Time Series DBMS

Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

axibase.com/docs/atsd/finance

www.graphengine.io

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

terminusdb.com

Technical documentation

www.graphengine.io/docs/manual

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

terminusdb.github.io/terminusdb/#

Developer

Axibase Corporation

Microsoft

DataChemist Ltd.

Initial release

2013

2010

1989

2018

Current release

15585

SQL Server 2022, November 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

MIT License

commercial

restricted free version is available

Open Source

GPL V3

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

.NET and C

C++

Prolog, Rust

Server operating systems

Linux

.NET

Linux
Windows

Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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 query language

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

Go
Java
PHP
Python
R
Ruby

C#
C++
F#
Visual Basic

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

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

horizontal partitioning

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.