DBMS > Dolt vs. Microsoft Access vs. Microsoft SQL Server vs. RDFox

System Properties Comparison Dolt vs. Microsoft Access vs. Microsoft SQL Server vs. RDFox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Microsofts flagship relational DBMS

High performance knowledge graph and semantic reasoning engine

Primary database model

Relational DBMS

Graph DBMS
RDF store

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Website

github.com/dolthub/dolt
www.dolthub.com

www.microsoft.com/en-us/microsoft-365/access

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

www.oxfordsemantic.tech

Technical documentation

docs.dolthub.com

developer.microsoft.com/en-us/access

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

docs.oxfordsemantic.tech

Developer

DoltHub Inc

Microsoft

Oxford Semantic Technologies

Initial release

2018

1992

1989

2017

Current release

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

6.0, Septermber 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

commercial

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Server operating systems

Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
macOS
Windows

Data scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
DAO
ODBC
OLE DB

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

RESTful HTTP API
SPARQL 1.1

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

C
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

since Access 2010 using the ACE-engine

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

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

none

yes, but depending on the SQL-Server Edition

replication via a shared file system

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

Only one user is configurable, and must be specified in the config file at startup

a simple user-level security was built in till version Access 2003

fine grained access rights according to SQL-standard

Roles, resources, and access types

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.