DBMS > Google BigQuery vs. Microsoft SQL Server vs. Teradata Aster vs. Vitess

System Properties Comparison Google BigQuery vs. Microsoft SQL Server vs. Teradata Aster vs. Vitess

Please select another system to include it in the comparison.

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

Large scale data warehouse service with append-only tables

Microsofts flagship relational DBMS

Platform for big data analytics on multistructured data sources and types

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

cloud.google.com/bigquery

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

vitess.io

Technical documentation

cloud.google.com/bigquery/docs

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

vitess.io/docs

Developer

Google

Microsoft

Teradata

The Linux Foundation, PlanetScale

Initial release

2010

1989

2005

2013

Current release

SQL Server 2022, November 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache Version 2.0, commercial licenses 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

C++

Server operating systems

hosted

Linux
Windows

Linux

Docker
Linux
macOS

Data scheme

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

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C#
C++
Java
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

R packages

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

yes

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

Multi-source replication
Source-replica 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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.