DBMS > Hyprcubd vs. Microsoft SQL Server vs. Qdrant vs. Snowflake vs. Splunk

System Properties Comparison Hyprcubd vs. Microsoft SQL Server vs. Qdrant vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Serverless Time Series DBMS

Microsofts flagship relational DBMS

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

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

hyprcubd.com (offline)

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

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

www.splunk.com

Technical documentation

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

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Hyprcubd, Inc.

Microsoft

Qdrant

Snowflake Computing Inc.

Splunk Inc.

Initial release

1989

2021

2014

2003

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2.0

commercial

Limited free edition and free developer edition available

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

Rust

Server operating systems

hosted

Linux
Windows

Docker
Linux
macOS
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

APIs and other access methods

gRPC (https)

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Collection-level replication

yes

Multi-source 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

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

token access

fine grained access rights according to SQL-standard

Key-based authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

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.