DBMS > SAP HANA vs. SQLite vs. Teradata vs. Vitess

System Properties Comparison SAP HANA vs. SQLite vs. Teradata vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used embeddable, in-process RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.sap.com/products/hana.html

www.sqlite.org

www.teradata.com

vitess.io

Technical documentation

help.sap.com/hana

www.sqlite.org/docs.html

docs.teradata.com

vitess.io/docs

Developer

SAP

Dwayne Richard Hipp

Teradata

The Linux Foundation, PlanetScale

Initial release

2010

2000

1984

2013

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.46.0 (23 May 2024), May 2024

Teradata Vantage 1.0 MU2, January 2019

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

Appliance or cloud-service

server-less

hosted
Linux

Docker
Linux
macOS

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

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

Server-side scripts

Stored procedures

SQLScript, R

yes

UDFs, stored procedures, table functions in parallel

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

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

yes

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.