DBMS > Microsoft Access vs. PostgreSQL vs. QuestDB

System Properties Comparison Microsoft Access vs. PostgreSQL vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

A high performance open source SQL database for time series data

Primary database model

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Relational DBMS

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

Score	96.72
Rank	#12	Overall
	#8	Relational DBMS

Score	663.42
Rank	#4	Overall
	#4	Relational DBMS

Score	3.10
Rank	#84	Overall
	#6	Time Series DBMS

Website

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

www.postgresql.org

questdb.io

Technical documentation

developer.microsoft.com/en-us/access

www.postgresql.org/docs

questdb.io/docs

Developer

Microsoft

PostgreSQL Global Development Group

www.postgresql.org/developer

QuestDB Technology Inc

Initial release

1992

1989

1989: Postgres, 1996: PostgreSQL

2014

Current release

1902 (16.0.11328.20222), March 2019

16.4, August 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

Apache 2.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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

C++

Java (Zero-GC), C++, Rust

Server operating systems

Windows

Not a real database server, but making use of DLLs

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free via InfluxDB Line Protocol

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

standard with numerous extensions

SQL with time-series extensions

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

partitioning by range, list and (since PostgreSQL 11) by hash

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

other methods possible by using 3rd party extensions

Source-replica replication with eventual consistency

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

but no files for transaction logging

ACID

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

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

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.