DBMS > Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. PlanetScale vs. TerarkDB

System Properties Comparison Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. PlanetScale vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

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	5.04
Rank	#71	Overall
	#39	Relational DBMS

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.75
Rank	#146	Overall
	#67	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

www.embarcadero.com/products/interbase

azure.microsoft.com/en-us/services/storage/tables

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

planetscale.com

github.com/bytedance/terarkdb

Technical documentation

docs.embarcadero.com/products/interbase

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

planetscale.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Embarcadero

Microsoft

PlanetScale

ByteDance, originally Terark

Initial release

1984

2012

1989

2020

2016

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

hosted

Linux
Windows

Docker
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

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

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

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

optimistic locking

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.