DBMS > Ingres vs. Microsoft SQL Server vs. OrientDB vs. Qdrant

System Properties Comparison Ingres vs. Microsoft SQL Server vs. OrientDB vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Well established RDBMS

Microsofts flagship relational DBMS

Multi-model DBMS (Document, Graph, Key/Value)

A high-performance vector database with neural network or semantic-based matching

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Vector DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

www.actian.com/databases/ingres

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

orientdb.org

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.actian.com/ingres

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

www.orientdb.com/docs/last/index.html

qdrant.tech/documentation

Developer

Actian Corporation

Microsoft

OrientDB LTD; CallidusCloud; SAP

Qdrant

Initial release

1974

originally developed at University Berkely in early 1970s

1989

2010

2021

Current release

11.2, May 2022

SQL Server 2022, November 2022

3.2.29, March 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache version 2

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java

Rust

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Windows

All OS with a Java JDK (>= JDK 6)

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

SQL-like query language, no joins

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

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

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

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

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes, but depending on the SQL-Server Edition

Multi-source replication

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

Key-based authentication

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.