DBMS > Google Cloud Bigtable vs. Microsoft SQL Server vs. SpaceTime vs. Teradata Aster vs. VictoriaMetrics

System Properties Comparison Google Cloud Bigtable vs. Microsoft SQL Server vs. SpaceTime vs. Teradata Aster vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

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

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

Platform for big data analytics on multistructured data sources and types

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Key-value store
Wide column store

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.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

cloud.google.com/bigtable

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

www.mireo.com/spacetime

victoriametrics.com

Technical documentation

cloud.google.com/bigtable/docs

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

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Google

Microsoft

Mireo

Teradata

VictoriaMetrics

Initial release

2015

1989

2020

2005

2018

Current release

SQL Server 2022, November 2022

v1.91, May 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache Version 2.0

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

Server operating systems

hosted

Linux
Windows

Linux

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

yes

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

ADO.NET
JDBC
ODBC
OLE DB

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

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

C#
C++
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

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

R packages

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

Fixed-grid hypercubes

Sharding

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

Real-time block device replication (DRBD)

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual 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

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.