DBMS > Microsoft SQL Server vs. mSQL vs. Oracle Berkeley DB vs. RDF4J

System Properties Comparison Microsoft SQL Server vs. mSQL vs. Oracle Berkeley DB vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used in-process key-value store

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

RDF store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Website

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

hughestech.com.au/products/msql

www.oracle.com/database/technologies/related/berkeleydb.html

rdf4j.org

Technical documentation

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

docs.oracle.com/cd/E17076_05/html/index.html

rdf4j.org/documentation

Developer

Microsoft

Hughes Technologies

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

1989

1994

2004

Current release

SQL Server 2022, November 2022

4.4, October 2021

18.1.40, May 2020

License

Commercial or Open Source

commercial

restricted free version is available

commercial

free licenses can be provided

Open Source

commercial license available

Open Source

Eclipse Distribution License (EDL), v1.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.

Implementation language

C++

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Java
PHP
Python

Server-side scripts

Stored procedures

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

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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.