DBMS > FileMaker vs. Graphite vs. Microsoft SQL Server vs. Trafodion vs. Warp 10

System Properties Comparison FileMaker vs. Graphite vs. Microsoft SQL Server vs. Trafodion vs. Warp 10

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Microsofts flagship relational DBMS

Transactional SQL-on-Hadoop DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store
Graph DBMS
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.75
Rank	#75	Overall
	#5	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

www.claris.com/filemaker

github.com/graphite-project/graphite-web

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

trafodion.apache.org

www.warp10.io

Technical documentation

www.claris.com/resources/documentation

graphite.readthedocs.io

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

trafodion.apache.org/documentation.html

www.warp10.io/content/02_Getting_started

Developer

Claris

a subsidiary of Apple

Chris Davis

Microsoft

Apache Software Foundation, originally developed by HP

SenX

Initial release

1983

2006

1989

2014

2015

Current release

19.4.1, November 2021

SQL Server 2022, November 2022

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

Apache License 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

Python

C++

C++, Java

Java

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
Unix

Linux
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

HTTP API
Sockets

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

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

PHP

JavaScript (Node.js)
Python

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

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

Java Stored Procedures

yes

WarpScript

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

none

yes, but depending on the SQL-Server Edition

yes, via HBase

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

based on HBase

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

locking

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

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.