DBMS > BigchainDB vs. Microsoft SQL Server vs. PostGIS vs. SAP SQL Anywhere vs. TimesTen

System Properties Comparison BigchainDB vs. Microsoft SQL Server vs. PostGIS vs. SAP SQL Anywhere vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Microsofts flagship relational DBMS

Spatial extension of PostgreSQL

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

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	1.35
Rank	#165	Overall
	#75	Relational DBMS

Website

www.bigchaindb.com

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

postgis.net

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

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

postgis.net/documentation

help.sap.com/docs/SAP_SQL_Anywhere

docs.oracle.com/database/timesten-18.1

Developer

Microsoft

SAP

formerly Sybase

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2016

1989

2005

1992

1998

Current release

SQL Server 2022, November 2022

3.4.2, February 2024

17, July 2015

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

AGPL v3

commercial

restricted free version is available

Open Source

GPL v2.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

Python

C++

Server operating systems

Linux

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

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

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

ADO.NET
HTTP API
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

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

user defined functions

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

PL/SQL

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

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

Source-replica replication

Database mirroring

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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,with MongoDB ord RethinkDB

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.