DBMS > Ingres vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Netezza

System Properties Comparison Ingres vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Netezza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Well established RDBMS

Globally distributed, horizontally scalable, multi-model database service

Database as a Service offering with high compatibility to Microsoft SQL Server

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Website

www.actian.com/databases/ingres

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/products/azure-sql/database

www.ibm.com/products/netezza

Technical documentation

docs.actian.com/ingres

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/azure-sql

Developer

Actian Corporation

Microsoft

IBM

Initial release

1974

originally developed at University Berkely in early 1970s

2014

2010

2000

Current release

11.2, May 2022

V12

License

Commercial or Open Source

commercial

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

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Linux

included in appliance

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC

JDBC
ODBC
OLE DB

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

yes

JavaScript

Transact SQL

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.