DBMS > Faircom DB vs. FileMaker vs. Linter vs. SAP HANA vs. TempoIQ

System Properties Comparison Faircom DB vs. FileMaker vs. Linter vs. SAP HANA vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

RDBMS for high security requirements

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.claris.com/filemaker

linter.ru

www.sap.com/products/hana.html

tempoiq.com (offline)

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.claris.com/resources/documentation

help.sap.com/hana

Developer

FairCom Corporation

Claris

a subsidiary of Apple

relex.ru

SAP

TempoIQ

Initial release

1979

1983

1990

2010

2012

Current release

V12, November 2020

19.4.1, November 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

ANSI C, C++

C and C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Appliance or cloud-service

Data scheme

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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, ANSI SQL with proprietary extensions

yes

via plugins

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Filemaker WebDirect
JDBC
ODBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC

HTTP API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

PHP

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

proprietary syntax with the possibility to convert from PL/SQL

SQLScript, R

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication, warm standby

since Version 14

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

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

fine grained access rights according to SQL-standard

yes

simple authentication-based access control

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.