DBMS > Google BigQuery vs. Sphinx vs. Vertica

System Properties Comparison Google BigQuery vs. Sphinx vs. Vertica

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

Open source search engine for searching in data from different sources, e.g. relational databases

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

Search engine

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	11.40
Rank	#43	Overall
	#27	Relational DBMS

Website

cloud.google.com/bigquery

sphinxsearch.com

www.vertica.com

Technical documentation

cloud.google.com/bigquery/docs

sphinxsearch.com/docs

vertica.com/documentation

Developer

Google

Sphinx Technologies Inc.

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2010

2001

2005

Current release

3.5.1, February 2023

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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.

Secondary indexes

yes

full-text index on all search fields

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

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

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; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.