DBMS > 4D vs. FileMaker vs. Microsoft SQL Server vs. MonetDB vs. SiteWhere

System Properties Comparison 4D vs. FileMaker vs. Microsoft SQL Server vs. MonetDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Microsofts flagship relational DBMS

A relational database management system that stores data in columns

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

www.4d.com

www.claris.com/filemaker

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

www.monetdb.org

github.com/sitewhere/sitewhere

Technical documentation

developer.4d.com

www.claris.com/resources/documentation

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

www.monetdb.org/Documentation

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Claris

a subsidiary of Apple

Microsoft

MonetDB BV

SiteWhere

Initial release

1984

1983

1989

2004

2010

Current release

v20, April 2023

19.4.1, November 2021

SQL Server 2022, November 2022

Dec2023 (11.49), December 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Mozilla Public License 2.0

Open Source

Common Public Attribution License Version 1.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

C++

Java

Server operating systems

OS X
Windows

iOS

client part only
Linux
OS X
Windows

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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

close to SQL 92

yes

via plugins

yes

SQL 2003 with some extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Filemaker WebDirect
JDBC
ODBC

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

PHP

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Server-side scripts

Stored procedures

yes

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

yes, in SQL, C, R

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 via remote tables

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication, warm standby

since Version 14

yes, but depending on the SQL-Server Edition

none

Source-replica replication available in experimental status

selectable replication factor

based on HBase

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

Concurrency

Support for concurrent manipulation of data

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

Users and groups

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.