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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

Microsofts flagship relational DBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

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

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

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

cloud.google.com/bigquery

linter.ru

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

solr.apache.org

Technical documentation

cloud.google.com/bigquery/docs

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

solr.apache.org/resources.html

Developer

Google

relex.ru

Microsoft

Apache Software Foundation

Initial release

2010

1990

1989

2006

Current release

SQL Server 2022, November 2022

9.5.0, February 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2

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

C++

Java

Server operating systems

hosted

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

Linux
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

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)

Java API
RESTful HTTP/JSON API

Supported programming languages

.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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

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

Java plugins

Triggers

yes

User configurable commands triggered on index changes

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

Source-replica replication

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

optimistic locking

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

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.