DBMS > Google BigQuery vs. Google Cloud Datastore vs. Microsoft Access vs. TDengine

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. Microsoft Access vs. TDengine

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.)

Time Series DBMS and big data platform

Primary database model

Secondary database models

Relational DBMS

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	2.48
Rank	#107	Overall
	#9	Time Series DBMS

Website

cloud.google.com/bigquery

cloud.google.com/datastore

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

github.com/taosdata/TDengine
tdengine.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

developer.microsoft.com/en-us/access

docs.tdengine.com

Developer

Google

Microsoft

TDEngine, previously Taos Data

Initial release

2010

2008

1992

2019

Current release

1902 (16.0.11328.20222), March 2019

3.0, August 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

AGPL V3, also commercial editions 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

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

Standard SQL with extensions for time-series applications

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

JDBC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

yes

since Access 2010 using the ACE-engine

Triggers

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

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)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a time-series database designed to help traditional industries overcome...
» more

Competitive advantages

High Performance at Any Scale: With its distributed scalable architecture that grows...
» more

Typical application scenarios

TDengine is purpose-built for Industry 4.0 and the Industrial IoT (IIoT) and particularly...
» more

Market metrics

TDengine has garnered over 23,000 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is free, open-source software released under the AGPLv3. TDengine Enterprise...
» more

News

Optimize Data Consolidation for Multi-Site Renewable Energy Operations
9 September 2024

Connect Power BI to TDengine
6 September 2024

Using Streams and Subscriptions for Alerting
5 September 2024

Solar Panel Monitoring: OPC UA Ingestion
2 September 2024

Time-Series Databases: A Game Changer for the Renewable Energy Industry
30 August 2024

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.