DBMS > Coveo vs. GridDB vs. HBase vs. Microsoft SQL Server

System Properties Comparison Coveo vs. GridDB vs. HBase vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Scalable in-memory time series database optimized for IoT and Big Data

Wide-column store based on Apache Hadoop and on concepts of BigTable

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Key-value store
Relational DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.coveo.com

griddb.net

hbase.apache.org

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

Technical documentation

docs.coveo.com

docs.griddb.net

hbase.apache.org/book.html

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

Developer

Coveo

Toshiba Corporation

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Initial release

2012

2013

2008

1989

Current release

5.1, August 2022

2.3.4, January 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache version 2

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

Java

C++

Server operating systems

hosted

Linux

Linux
Unix
Windows

using Cygwin

Linux
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

options to bring your own types, AVRO

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

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

Supported programming languages

C#
Java
JavaScript
Python

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Server-side scripts

Stored procedures

yes

Coprocessors in Java

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID at container level

Single row ACID (across millions of columns)

ACID

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

granular access controls, API key management, content filters

Access rights for users can be defined per database

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.