DBMS > Google BigQuery vs. Microsoft SQL Server vs. Sqrrl vs. Warp 10

System Properties Comparison Google BigQuery vs. Microsoft SQL Server vs. Sqrrl vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service with append-only tables

Microsofts flagship relational DBMS

Adaptable, secure NoSQL built on Apache Accumulo

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

cloud.google.com/bigquery

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

sqrrl.com

www.warp10.io

Technical documentation

cloud.google.com/bigquery/docs

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

www.warp10.io/content/02_Getting_started

Developer

Google

Microsoft

Amazon

originally Sqrrl Data, Inc.

SenX

Initial release

2010

1989

2012

2015

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

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

Java

Server operating systems

hosted

Linux
Windows

Linux

Linux
OS X
Windows

Data scheme

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

yes

APIs and other access methods

RESTful HTTP/JSON API

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

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

HTTP API
Jupyter
WebSocket

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

yes

WarpScript

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

making use of Hadoop

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

selectable replication factor

making use of Hadoop

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Atomic updates per row, document, or graph entity

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.