DBMS > Microsoft SQL Server vs. Realm vs. SAP HANA vs. SiteWhere vs. Trafodion

System Properties Comparison Microsoft SQL Server vs. Realm vs. SAP HANA vs. SiteWhere vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Microsofts flagship relational DBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

In-memory, column based data store. Available as appliance or cloud service

M2M integration platform for persisting/querying time series data

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

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

realm.io

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

trafodion.apache.org

Technical documentation

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

realm.io/docs

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

trafodion.apache.org/documentation.html

Developer

Microsoft

Realm, acquired by MongoDB in May 2019

SAP

SiteWhere

Apache Software Foundation, originally developed by HP

Initial release

1989

2014

2010

2014

Current release

SQL Server 2022, November 2022

2.0 SPS07 (April 4, 2023), April 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C++, Java

Server operating systems

Linux
Windows

Android
Backend: server-less
iOS
Windows

Appliance or cloud-service

Linux
OS X
Windows

Linux

Data scheme

yes

predefined 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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

JDBC
ODBC

HTTP REST

ADO.NET
JDBC
ODBC

Supported programming languages

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

.Net
Java

with Android only
Objective-C
React Native
Swift

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

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

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Java Stored Procedures

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

yes

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

none

yes

selectable replication factor

based on HBase

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

In-memory capabilities

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

yes

In-Memory realm

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

Users with fine-grained authorization concept

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.