DBMS > FatDB vs. RavenDB vs. SAP Adaptive Server vs. Snowflake

System Properties Comparison FatDB vs. RavenDB vs. SAP Adaptive Server vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

ravendb.net

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

www.snowflake.com

Technical documentation

ravendb.net/docs

help.sap.com/docs/SAP_ASE

docs.snowflake.net/manuals/index.html

Developer

FatCloud

Hibernating Rhinos

SAP, Sybase

Snowflake Computing Inc.

Initial release

2012

2010

1987

2014

Current release

5.4, July 2022

16.0

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

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

C and C++

Server operating systems

Windows

Linux
macOS
Raspberry Pi
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

hosted

Data scheme

schema-free

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

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (RQL)

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

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

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Java and Transact-SQL

user defined functions

Triggers

yes

via applications

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

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.

User concepts

Access control

Can implement custom security layer via applications

Authorization levels configured per client per database

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.