DBMS > Firebase Realtime Database vs. HEAVY.AI vs. Microsoft SQL Server

System Properties Comparison Firebase Realtime Database vs. HEAVY.AI vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Microsofts flagship relational DBMS

Primary database model

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	17.08
Rank	#38	Overall
	#6	Document stores

Score	3.01
Rank	#111	Overall
	#55	Relational DBMS

Score	903.83
Rank	#3	Overall
	#3	Relational DBMS

Website

firebase.google.com/products/realtime-database

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

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

Technical documentation

firebase.google.com/docs/database

docs.heavy.ai

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

Developer

Google

acquired by Google 2014

HEAVY.AI, Inc.

Microsoft

Initial release

2012

2016

1989

Current release

5.10, January 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

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 CUDA

C++

Server operating systems

hosted

Linux

Linux
Windows

Data scheme

schema-free

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

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

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

Supported programming languages

Java
JavaScript
Objective-C

All languages supporting JDBC/ODBC/Thrift
Python

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

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

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

yes, based on authentication and database rules

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.