DBMS > Google Cloud Bigtable vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. SpaceTime

System Properties Comparison Google Cloud Bigtable vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. SpaceTime

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.

Microsofts flagship relational DBMS

Widely used in-process key-value store

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Key-value store
Wide column store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Spatial DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.00
Rank	#396	Overall
	#8	Spatial DBMS

Website

cloud.google.com/bigtable

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

www.oracle.com/database/technologies/related/berkeleydb.html

www.mireo.com/spacetime

Technical documentation

cloud.google.com/bigtable/docs

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

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Google

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Mireo

Initial release

2015

1989

1994

2020

Current release

SQL Server 2022, November 2022

18.1.40, May 2020

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

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++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

yes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

A subset of ANSI SQL is implemented

APIs and other access methods

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

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

RESTful HTTP API

Supported programming languages

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

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C#
C++
Python

Server-side scripts

Stored procedures

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

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes, but depending on the SQL-Server Edition

Source-replica replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

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)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

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

fine grained access rights according to SQL-standard

yes

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.