DBMS > Microsoft SQL Server vs. TimescaleDB vs. VictoriaMetrics vs. WakandaDB

System Properties Comparison Microsoft SQL Server vs. TimescaleDB vs. VictoriaMetrics vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Time Series DBMS

Object oriented DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

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

www.timescale.com

victoriametrics.com

wakanda.github.io

Technical documentation

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

docs.timescale.com

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

wakanda.github.io/doc

Developer

Microsoft

Timescale

VictoriaMetrics

Wakanda SAS

Initial release

1989

2017

2018

2012

Current release

SQL Server 2022, November 2022

2.15.0, May 2024

v1.91, May 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

AGPLv3, extended commercial license available

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

C++

C++, JavaScript

Server operating systems

Linux
Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
OpenBSD

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

RESTful HTTP API

Supported programming languages

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

JavaScript

Server-side scripts

Stored procedures

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

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Source-replica replication with hot standby and reads on replicas

Synchronous replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

fine grained access rights according to SQL-standard

yes

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.