DBMS > Bangdb vs. Google BigQuery vs. Linter vs. Microsoft SQL Server

System Properties Comparison Bangdb vs. Google BigQuery vs. Linter vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

Microsofts flagship relational DBMS

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.15
Rank	#334	Overall
	#45	Document stores
	#31	Graph DBMS
	#31	Time Series DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.10
Rank	#350	Overall
	#153	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

bangdb.com

cloud.google.com/bigquery

linter.ru

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

Technical documentation

docs.bangdb.com

cloud.google.com/bigquery/docs

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

Developer

Sachin Sinha, BangDB

Google

relex.ru

Microsoft

Initial release

2012

2010

1990

1989

Current release

BangDB 2.0, October 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

BSD 3

commercial

restricted free version is 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.

Implementation language

C, C++

C and C++

C++

Server operating systems

Linux

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

APIs and other access methods

Proprietary protocol
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

Supported programming languages

C
C#
C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

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

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Source-replica replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

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

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.