DBMS > Microsoft Azure SQL Database vs. NSDb vs. SQLite vs. VoltDB

System Properties Comparison Microsoft Azure SQL Database vs. NSDb vs. SQLite vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

nsdb.io

www.sqlite.org

www.voltdb.com

Technical documentation

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

nsdb.io/Architecture

www.sqlite.org/docs.html

docs.voltdb.com

Developer

Microsoft

Dwayne Richard Hipp

VoltDB Inc.

Initial release

2010

2017

2000

2010

Current release

V12

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, Scala

Java, C++

Server operating systems

hosted

Linux
macOS

server-less

Linux
OS X

for development

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

not rigid because of 'dynamic typing' concept.

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

Java
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.