DBMS > Linter vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. TerminusDB

System Properties Comparison Linter vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

RDBMS for high security requirements

Microsofts flagship relational DBMS

Widely used in-process key-value store

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

linter.ru

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

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

terminusdb.com

Technical documentation

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

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

terminusdb.github.io/terminusdb/#

Developer

relex.ru

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

DataChemist Ltd.

Initial release

1990

1989

1994

2018

Current release

SQL Server 2022, November 2022

18.1.40, May 2020

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

commercial license available

Open Source

GPL V3

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 and C++

C++

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

Prolog, Rust

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

schema-free

yes

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

SQL interfaced based on SQLite is available

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

.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

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

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

none

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

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-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.