DBMS > AlaSQL vs. Greenplum vs. Infobright vs. Microsoft Azure SQL Database vs. MySQL

System Properties Comparison AlaSQL vs. Greenplum vs. Infobright vs. Microsoft Azure SQL Database vs. MySQL

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

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	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

alasql.org

greenplum.org

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

Technical documentation

github.com/AlaSQL/alasql

docs.greenplum.org

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Pivotal Software Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2005

2010

1995

Current release

7.0.0, September 2023

V12

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

JavaScript

C++

C and C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
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

since Version 4.2

yes

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

C
Java
Perl
Python
R

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes, with always 3 replicas available

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

exploiting MySQL or PostgreSQL frontend capabilities

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.