DBMS > MarkLogic vs. Microsoft SQL Server vs. NSDb vs. STSdb

System Properties Comparison MarkLogic vs. Microsoft SQL Server vs. NSDb vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Operational and transactional Enterprise NoSQL database

Microsofts flagship relational DBMS

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.marklogic.com

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

nsdb.io

github.com/STSSoft/STSdb4

Technical documentation

docs.marklogic.com

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

nsdb.io/Architecture

Developer

MarkLogic Corp.

Microsoft

STS Soft SC

Initial release

2001

1989

2017

2011

Current release

11.0, December 2022

SQL Server 2022, November 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

restricted free version is available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

GPLv2, commercial license available

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.

Implementation language

C++

Java, Scala

Server operating systems

Linux
OS X
Windows

Linux
Windows

Linux
macOS

Windows

Data scheme

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

primitive types and user defined types (classes)

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

all fields are automatically indexed

SQL

Support of SQL

yes

SQL92

yes

SQL-like query language

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

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

gRPC
HTTP REST
WebSocket

.NET Client API

Supported programming languages

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

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

Java
Scala

C#
Java

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

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.