DBMS > FileMaker vs. Google Cloud Datastore vs. Microsoft Access vs. SAP HANA

System Properties Comparison FileMaker vs. Google Cloud Datastore vs. Microsoft Access vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	49.73
Rank	#20	Overall
	#14	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

www.claris.com/filemaker

cloud.google.com/datastore

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

www.sap.com/products/hana.html

Technical documentation

www.claris.com/resources/documentation

cloud.google.com/datastore/docs

developer.microsoft.com/en-us/access

help.sap.com/hana

Developer

Claris

a subsidiary of Apple

Google

Microsoft

SAP

Initial release

1983

2008

1992

2010

Current release

19.4.1, November 2021

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

hosted

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

A http query request can return the data in XML format

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

using Google App Engine

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

simple rights management via user accounts and connection to external directory services

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

yes

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.