DBMS > Microsoft SQL Server vs. RavenDB vs. searchxml vs. TempoIQ

System Properties Comparison Microsoft SQL Server vs. RavenDB vs. searchxml vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

DBMS for structured and unstructured content wrapped with an application server

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Document store

Native XML DBMS
Search engine

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

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

ravendb.net

www.searchxml.net/category/products

tempoiq.com (offline)

Technical documentation

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

ravendb.net/docs

www.searchxml.net/support/handouts

Developer

Microsoft

Hibernating Rhinos

informationpartners gmbh

TempoIQ

Initial release

1989

2010

2015

2012

Current release

SQL Server 2022, November 2022

5.4, July 2022

1.0

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

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

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

yes

SQL-like query language (RQL)

APIs and other access methods

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP API

Supported programming languages

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

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

C++

most other programming languages supported via APIs

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

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

yes

on the application server

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Multi-source replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

multiple readers, single writer

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

Authorization levels configured per client per database

Domain, group and role-based access control at the document level and for application services

simple authentication-based access control

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.