DBMS > Altibase vs. Apache Impala vs. Axibase vs. Google Cloud Datastore vs. Microsoft SQL Server

System Properties Comparison Altibase vs. Apache Impala vs. Axibase vs. Google Cloud Datastore vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Analytic DBMS for Hadoop

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

altibase.com

impala.apache.org

axibase.com/docs/atsd/finance

cloud.google.com/datastore

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

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

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

Developer

Altibase

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Axibase Corporation

Google

Microsoft

Initial release

1999

2013

2008

1989

Current release

v7.3, 2023, August 2023

4.1.0, June 2022

15585

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

Apache Version 2

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

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

AIX
HP-UX
Linux

Linux

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

SQL-like DML and DDL statements

SQL-like query language

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

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

Supported programming languages

C
C++
Java

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

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

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

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

user defined functions and integration of map-reduce

yes

using Google App Engine

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

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

fine grained access rights according to SQL-standard

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.