DBMS > Graph Engine vs. Interbase vs. Microsoft SQL Server vs. RRDtool

System Properties Comparison Graph Engine vs. Interbase vs. Microsoft SQL Server vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Light-weight proven RDBMS

originally from Borland

Microsofts flagship relational DBMS

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

www.graphengine.io

www.embarcadero.com/products/interbase

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

oss.oetiker.ch/rrdtool

Technical documentation

www.graphengine.io/docs/manual

docs.embarcadero.com/products/interbase

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

oss.oetiker.ch/rrdtool/doc

Developer

Microsoft

Embarcadero

Microsoft

Tobias Oetiker

Initial release

2010

1984

1989

1999

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

1.8.0, 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

GPL V2 and FLOSS

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

.NET and C

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

.NET

Android
iOS
Linux
OS X
Windows

Linux
Windows

HP-UX
Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

export as XML data possible

yes

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

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

in-process shared library
Pipes

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

Multiversion concurreny control

yes

by using the rrdcached daemon

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.