DBMS > Graph Engine vs. Infobright vs. mSQL vs. SAP Adaptive Server vs. Snowflake

System Properties Comparison Graph Engine vs. Infobright vs. mSQL vs. SAP Adaptive Server vs. Snowflake

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

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.graphengine.io

ignitetech.com/softwarelibrary/infobrightdb

hughestech.com.au/products/msql

www.sap.com/products/technology-platform/sybase-ase.html

www.snowflake.com

Technical documentation

www.graphengine.io/docs/manual

help.sap.com/docs/SAP_ASE

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Ignite Technologies Inc.; formerly InfoBright Inc.

Hughes Technologies

SAP, Sybase

Snowflake Computing Inc.

Initial release

2010

2005

1994

1987

2014

Current release

4.4, October 2021

16.0

License

Commercial or Open Source

Open Source

MIT License

commercial

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

commercial

free licenses can be provided

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

.NET and C

C and C++

Server operating systems

.NET

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC

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

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

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

C
C++
Delphi
Java
Perl
PHP
Tcl

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Java and Transact-SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.