DBMS > Interbase vs. Memcached vs. Microsoft SQL Server vs. Tkrzw

System Properties Comparison Interbase vs. Memcached vs. Microsoft SQL Server vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

In-memory key-value store, originally intended for caching

Microsofts flagship relational DBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.embarcadero.com/products/interbase

www.memcached.org

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

dbmx.net/tkrzw

Technical documentation

docs.embarcadero.com/products/interbase

github.com/memcached/memcached/wiki

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

Developer

Embarcadero

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Mikio Hirabayashi

Initial release

1984

2003

1989

2020

Current release

InterBase 2020, December 2019

1.6.25, March 2024

SQL Server 2022, November 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

restricted free version is available

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.

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++

Server operating systems

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Proprietary protocol

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

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

C++
Java
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

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

none

Repcached, a Memcached patch, provides this functionallity

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

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

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

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.