DBMS > Axibase vs. Heroic vs. HyperSQL vs. Microsoft SQL Server vs. Qdrant

System Properties Comparison Axibase vs. Heroic vs. HyperSQL vs. Microsoft SQL Server vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Microsofts flagship relational DBMS

A high-performance vector database with neural network or semantic-based matching

Primary database model

Time Series DBMS

Relational DBMS

Vector DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

axibase.com/docs/atsd/finance

github.com/spotify/heroic

hsqldb.org

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

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

spotify.github.io/heroic

hsqldb.org/web/hsqlDocsFrame.html

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

qdrant.tech/documentation

Developer

Axibase Corporation

Spotify

Microsoft

Qdrant

Initial release

2013

2014

2001

1989

2021

Current release

15585

2.7.2, June 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

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

Open Source

Apache 2.0

Open Source

based on BSD license

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

C++

Rust

Server operating systems

Linux

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

Numbers, Strings, Geo, Boolean

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

via Elasticsearch

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

Go
Java
PHP
Python
R
Ruby

All languages supporting JDBC/ODBC
Java

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

Java, SQL

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

yes, but depending on the SQL-Server Edition

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency, tunable 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

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

Key-based authentication

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.