DBMS > AnzoGraph DB vs. FatDB vs. Microsoft SQL Server vs. SiteWhere

System Properties Comparison AnzoGraph DB vs. FatDB vs. Microsoft SQL Server vs. SiteWhere

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

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Microsofts flagship relational DBMS

M2M integration platform for persisting/querying time series data

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

cambridgesemantics.com/anzograph

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

github.com/sitewhere/sitewhere

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

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

sitewhere1.sitewhere.io/index.html

Developer

Cambridge Semantics

FatCloud

Microsoft

SiteWhere

Initial release

2018

2012

1989

2010

Current release

2.3, January 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

free trial version available

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

yes

predefined scheme

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

SPARQL and SPARQL* as primary query language. Cypher preview.

Via inetgration in SQL Server

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

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

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

HTTP REST

Supported programming languages

C++
Java
Python

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

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

via applications

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

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication factor

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

User concepts

Access control

Access rights for users and roles

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.