DBMS > Apache Phoenix vs. Kyligence Enterprise vs. Microsoft SQL Server vs. Qdrant vs. SAP SQL Anywhere

System Properties Comparison Apache Phoenix vs. Kyligence Enterprise vs. Microsoft SQL Server vs. Qdrant vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A distributed analytics engine for big data, built on top of Apache Kylin

Microsofts flagship relational DBMS

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Vector DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

phoenix.apache.org

kyligence.io/kyligence-enterprise

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

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

phoenix.apache.org

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

qdrant.tech/documentation

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

Kyligence, Inc.

Microsoft

Qdrant

SAP

formerly Sybase

Initial release

2014

2016

1989

2021

1992

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

SQL Server 2022, November 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

Java

C++

Rust

Server operating systems

Linux
Unix
Windows

Linux

Linux
Windows

Docker
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC

JDBC
ODBC
RESTful HTTP API

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Collection-level replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

fine grained access rights according to SQL-standard

Key-based authentication

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.