DBMS > Graph Engine vs. HEAVY.AI vs. Microsoft SQL Server vs. OceanBase

System Properties Comparison Graph Engine vs. HEAVY.AI vs. Microsoft SQL Server vs. OceanBase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Microsofts flagship relational DBMS

A distributed, high available RDBMS compatible with Oracle and MySQL

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Wide column store

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

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.56
Rank	#153	Overall
	#71	Relational DBMS

Website

www.graphengine.io

github.com/heavyai/heavydb
www.heavy.ai

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

en.oceanbase.com

Technical documentation

www.graphengine.io/docs/manual

docs.heavy.ai

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

en.oceanbase.com/docs/oceanbase-database

Developer

Microsoft

HEAVY.AI, Inc.

Microsoft

OceanBase

previously Alibaba and Ant Group

Initial release

2010

2016

1989

2011

Current release

5.10, January 2022

SQL Server 2022, November 2022

3.2.3, March 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Open Source

Commercial license available

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.

Implementation language

.NET and C

C++ and CUDA

C++

Server operating systems

.NET

Linux

Linux
Windows

Linux

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

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

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

Server-side scripts

Stored procedures

yes

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

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

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

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, but depending on the SQL-Server Edition

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Access rights for users, groups and roles according to SQL-standard

More information provided by the system vendor

Specific characteristics

OceanBase Database is the world’s only native distributed database that has set new...
» more

Competitive advantages

High Availability : The five IDCs across three sites disaster recovery solution sets...
» more

Key customers

OceanBase Database has helped over 400 customers across industries upgrade their...
» more

Market metrics

TPC-C No.1 Performance , achieved a result of 707.35 million tpmC in the TPC-C benchmark...
» more

Licensing and pricing models

Mulan PubL v2 license for open source community edition. Commercial license for enterprise...
» more

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.