DBMS > DolphinDB vs. Microsoft SQL Server vs. PlanetScale vs. PostGIS

System Properties Comparison DolphinDB vs. Microsoft SQL Server vs. PlanetScale vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

Microsofts flagship relational DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Spatial extension of PostgreSQL

Primary database model

Time Series DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.dolphindb.com

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

planetscale.com

postgis.net

Technical documentation

docs.dolphindb.cn/en/help200/index.html

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

planetscale.com/docs

postgis.net/documentation

Developer

DolphinDB, Inc

Microsoft

PlanetScale

Initial release

2018

1989

2020

2005

Current release

v2.00.4, January 2022

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

commercial

free community version available

commercial

restricted free version is available

commercial

Open Source

GPL v2.0

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

Server operating systems

Linux
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

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

with proprietary extensions

yes

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

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

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

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

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Administrators, Users, Groups

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.