DBMS > Greenplum vs. MaxDB vs. Microsoft SQL Server vs. Solr

System Properties Comparison Greenplum vs. MaxDB vs. Microsoft SQL Server vs. Solr

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.

A robust and reliable RDBMS optimized to run all major SAP solutions

Microsofts flagship relational DBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

greenplum.org

maxdb.sap.com

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

solr.apache.org

Technical documentation

docs.greenplum.org

maxdb.sap.com/documentation

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

solr.apache.org/resources.html

Developer

Pivotal Software Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

Apache Software Foundation

Initial release

2005

1984

1989

2006

Current release

7.0.0, September 2023

7.9.10.12, February 2024

SQL Server 2022, November 2022

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Limited community edition free

commercial

restricted free version is available

Open Source

Apache Version 2

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

Linux
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

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

Java API
RESTful HTTP/JSON API

Supported programming languages

C
Java
Perl
Python
R

.Net
C#
Java
Perl
PHP
Python

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

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

Java plugins

Triggers

yes

User configurable commands triggered on index changes

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

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

yes

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.