DBMS > Greenplum vs. Interbase vs. Microsoft SQL Server vs. PlanetScale

System Properties Comparison Greenplum vs. Interbase vs. Microsoft SQL Server vs. PlanetScale

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Light-weight proven RDBMS

originally from Borland

Microsofts flagship relational DBMS

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

Primary database model

Relational 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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

greenplum.org

www.embarcadero.com/products/interbase

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

planetscale.com

Technical documentation

docs.greenplum.org

docs.embarcadero.com/products/interbase

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

planetscale.com/docs

Developer

Pivotal Software Inc.

Embarcadero

Microsoft

PlanetScale

Initial release

2005

1984

1989

2020

Current release

7.0.0, September 2023

InterBase 2020, December 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

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

Android
iOS
Linux
OS X
Windows

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

since Version 4.2

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
Java
Perl
Python
R

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

Interbase procedure and trigger language

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Interbase Change Views

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.