DBMS > Google Cloud Bigtable vs. Hive vs. Microsoft SQL Server vs. RavenDB

System Properties Comparison Google Cloud Bigtable vs. Hive vs. Microsoft SQL Server vs. RavenDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

cloud.google.com/bigtable

hive.apache.org

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

ravendb.net

Technical documentation

cloud.google.com/bigtable/docs

cwiki.apache.org/confluence/display/Hive/Home

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

ravendb.net/docs

Developer

Google

Apache Software Foundation

initially developed by Facebook

Microsoft

Hibernating Rhinos

Initial release

2015

2012

1989

2010

Current release

3.1.3, April 2022

SQL Server 2022, November 2022

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license 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.

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

Java

C++

Server operating systems

hosted

All OS with a Java VM

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

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

SQL-like DML and DDL statements

yes

SQL-like query language (RQL)

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
Thrift

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

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

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

C++
Java
PHP
Python

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

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

yes, but depending on the SQL-Server Edition

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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.

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

ACID, Cluster-wide transaction available

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.