DBMS > Apache Drill vs. FileMaker vs. Microsoft SQL Server vs. PostGIS vs. Qdrant

System Properties Comparison Apache Drill vs. FileMaker vs. Microsoft SQL Server vs. PostGIS vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Microsofts flagship relational DBMS

Spatial extension of PostgreSQL

A high-performance vector database with neural network or semantic-based matching

Primary database model

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Vector DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

drill.apache.org

www.claris.com/filemaker

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

postgis.net

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

drill.apache.org/docs

www.claris.com/resources/documentation

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

postgis.net/documentation

qdrant.tech/documentation

Developer

Apache Software Foundation

Claris

a subsidiary of Apple

Microsoft

Qdrant

Initial release

2012

1983

1989

2005

2021

Current release

1.20.3, January 2023

19.4.1, November 2021

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

GPL v2.0

Open Source

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

Implementation language

C++

Rust

Server operating systems

Linux
OS X
Windows

iOS

client part only
Linux
OS X
Windows

Linux
Windows

Docker
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

via plugins

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Filemaker WebDirect
JDBC
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

C++

PHP

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

Key-based authentication

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.