DBMS > Greenplum vs. Microsoft SQL Server vs. Postgres-XL vs. TimesTen vs. Yanza

System Properties Comparison Greenplum vs. Microsoft SQL Server vs. Postgres-XL vs. TimesTen vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Microsofts flagship relational DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

In-Memory RDBMS compatible to Oracle

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

greenplum.org

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

www.postgres-xl.org

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

yanza.com

Technical documentation

docs.greenplum.org

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

www.postgres-xl.org/documentation

docs.oracle.com/database/timesten-18.1

Developer

Pivotal Software Inc.

Microsoft

Oracle, TimesTen Performance Software, HP

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

Yanza

Initial release

2005

1989

2014

since 2012, originally named StormDB

1998

2015

Current release

7.0.0, September 2023

SQL Server 2022, November 2022

10 R1, October 2018

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Mozilla public license

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Linux
Windows

Linux
macOS

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

Windows

Data scheme

yes

schema-free

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

since Version 4.2

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC
ODBC

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

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

C
Java
Perl
Python
R

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Java
PL/SQL

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

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

user defined functions

PL/SQL

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

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.