DBMS > Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Spark SQL vs. Teradata

System Properties Comparison Interbase vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Spark SQL vs. Teradata

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

www.embarcadero.com/products/interbase

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

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

spark.apache.org/sql

www.teradata.com

Technical documentation

docs.embarcadero.com/products/interbase

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

spark.apache.org/docs/latest/sql-programming-guide.html

docs.teradata.com

Developer

Embarcadero

Microsoft

Apache Software Foundation

Teradata

Initial release

1984

2012

1989

2014

1984

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

3.5.0 ( 2.13), September 2023

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache 2.0

commercial

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

Scala

Server operating systems

Android
iOS
Linux
OS X
Windows

hosted

Linux
Windows

Linux
OS X
Windows

hosted
Linux

Data scheme

yes

schema-free

yes

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL 2016 + extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

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

JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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

Java
Python
R
Scala

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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

yes

UDFs, stored procedures, table functions in parallel

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

yes, utilizing Spark Core

Sharding

Hashing

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

none

Multi-source replication
Source-replica replication

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

optimistic locking

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

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

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.