DBMS > GeoMesa vs. LevelDB vs. Microsoft Access vs. Microsoft SQL Server vs. PostGIS

System Properties Comparison GeoMesa vs. LevelDB vs. Microsoft Access vs. Microsoft SQL Server vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.geomesa.org

github.com/google/leveldb

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

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

postgis.net

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

github.com/google/leveldb/blob/main/doc/index.md

developer.microsoft.com/en-us/access

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

postgis.net/documentation

Developer

CCRi and others

Google

Microsoft

Initial release

2014

2011

1992

1989

2005

Current release

5.0.0, May 2024

1.23, February 2021

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

GPL v2.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.

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

Scala

C++

Server operating systems

Illumos
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux
Windows

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

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

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

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

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

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

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.