DBMS > Amazon CloudSearch vs. Google BigQuery vs. Microsoft Access vs. Sphinx

System Properties Comparison Amazon CloudSearch vs. Google BigQuery vs. Microsoft Access vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Large scale data warehouse service with append-only tables

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Primary database model

Search engine

Relational DBMS

Search engine

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

aws.amazon.com/cloudsearch

cloud.google.com/bigquery

www.microsoft.com/en-us/microsoft-365/access

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

sphinxsearch.com/docs

Developer

Amazon

Google

Microsoft

Sphinx Technologies Inc.

Initial release

2012

2010

1992

2001

Current release

1902 (16.0.11328.20222), March 2019

3.5.1, February 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

GPL version 2, commercial licence 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++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

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

In-memory capabilities

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

User concepts

Access control

authentication via encrypted signatures

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

a simple user-level security was built in till version Access 2003

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.