DBMS > Microsoft SQL Server vs. Tibero vs. Vitess vs. YottaDB

System Properties Comparison Microsoft SQL Server vs. Tibero vs. Vitess vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

A secure RDBMS, designed for easy portability from Oracle

Scalable, distributed, cloud-native DBMS, extending MySQL

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

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

us.tmaxsoft.com/products/tibero

vitess.io

yottadb.com

Technical documentation

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

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

vitess.io/docs

yottadb.com/resources/documentation

Developer

Microsoft

TmaxSoft

The Linux Foundation, PlanetScale

YottaDB, LLC

Initial release

1989

2003

2013

2001

Current release

SQL Server 2022, November 2022

6, April 2015

15.0.2, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

AGPL 3.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++

C and Assembler

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS

Docker
Linux

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

by using the Octo plugin

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

ADO.NET
JDBC
MySQL protocol
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
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
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

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

Persistent Stored Procedure (PSM)

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

horizontal partitioning

by range, hash, list or composite

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

yes

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

planned for next version

yes

User concepts

Access control

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

Users with fine-grained authorization concept

no user groups or roles

Users and groups based on OS-security mechanisms

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.