DBMS > Microsoft Azure SQL Database vs. Microsoft SQL Server vs. OpenEdge vs. Vitess

System Properties Comparison Microsoft Azure SQL Database vs. Microsoft SQL Server vs. OpenEdge vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

Microsofts flagship relational DBMS

Application development environment with integrated database management system

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

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	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

azure.microsoft.com/en-us/products/azure-sql/database

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

www.progress.com/openedge

vitess.io

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

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

documentation.progress.com/output/ua/OpenEdge_latest

vitess.io/docs

Developer

Microsoft

Progress Software Corporation

The Linux Foundation, PlanetScale

Initial release

2010

1989

1984

2013

Current release

V12

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

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

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

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

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

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

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

Progress proprietary ABL (Advanced Business Language)

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

Transact SQL

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

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

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes, but depending on the SQL-Server Edition

Source-replica replication

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

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

fine grained access rights according to SQL-standard

Users and groups

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.