DBMS > Databend vs. Microsoft Access vs. Microsoft SQL Server vs. VoltDB

System Properties Comparison Databend vs. Microsoft Access vs. Microsoft SQL Server vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

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

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

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

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

www.voltdb.com

Technical documentation

docs.databend.com

developer.microsoft.com/en-us/access

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

docs.voltdb.com

Developer

Databend Labs

Microsoft

VoltDB Inc.

Initial release

2021

1992

1989

2010

Current release

1.0.59, April 2023

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

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

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

Rust

C++

Java, C++

Server operating systems

hosted
Linux
macOS

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
OS X

for development

Data scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

only a subset of SQL 99

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

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#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

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

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

but no files for transaction logging

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

but no files for transaction logging

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

Users with fine-grained authorization concept, user roles

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

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.