DBMS > FileMaker vs. H2GIS vs. Microsoft SQL Server vs. PlanetScale vs. YDB

System Properties Comparison FileMaker vs. H2GIS vs. Microsoft SQL Server vs. PlanetScale vs. YDB

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of H2

Microsofts flagship relational DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Relational DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.claris.com/filemaker

www.h2gis.org

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

planetscale.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

www.claris.com/resources/documentation

www.h2gis.org/docs/home

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

planetscale.com/docs

ydb.tech/en/docs

Developer

Claris

a subsidiary of Apple

CNRS

Microsoft

PlanetScale

Yandex

Initial release

1983

2013

1989

2020

2019

Current release

19.4.1, November 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

commercial

restricted free version is available

commercial

Open Source

Apache 2.0; commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
Windows

Docker
Linux
macOS

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

yes

with proprietary extensions

SQL-like query language (YQL)

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

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

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

PHP

Java

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

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

based on H2

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

yes

proprietary syntax

Triggers

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

Source-replica replication, warm standby

since Version 14

yes

based on H2

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

yes

based on H2

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access rights defined for Yandex Cloud users

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.